deso-protocol / deso-protocol/backend

/transaction-info: add creator's pubkey to txindex metadata

Open
#298 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
139
Forks
84
PR merge metrics
No merged PRs in 30d

Description

In tandem with #297:

In `/transaction-info`, txindex metadata for both CC/DAO transfers identifies the creator by username instead of pubkey, for example:

```json
"CreatorCoinTransferTxindexMetadata": {
"CreatorUsername": "BeActive",
"CreatorCoinToTransferNanos": 10000,
"DiamondLevel": 0,
"PostHashHex": ""
}
```

This is really bad since AFAIK usernames are volatile and, even if they're not in case of already issued CCs/DAOs, it would require a second RPC call in order to grab the name's pubkey.

I would suggest improving the output of `/transaction-info` by adding the creator's pubkey in the txindex metadata.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start at the /transaction-info endpoint and trace the txindex metadata for CreatorCoin and DAO transfers. Confirm how creator identity is currently serialized, then update the output so both metadata types include the creator's public key alongside the existing username; done means the endpoint returns that key for both transfer types.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
api, backend-api-design
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.