Add Bridges #7
Add Bridges #7
Conversation
schemas/bridge/SCHEMA.md
Outdated
| | Property | Description | Type | | ||
| |-------------------------|-----------------------------------------------------------|--------| | ||
| | timestamp | The timestamp of the transaction. | number | | ||
| | block_number | The block number of the transaction. | number | | ||
| | transaction_hash | The hash of the transaction this bridge originated from. | string | | ||
| | source_chain_id | The source standard chain ID. | number | | ||
| | destination_chain_id | The destination standard chain ID. | number | | ||
| | volume_usd | The volume of the transaction in USD. | number | | ||
| | user_address | The address of the user initiating the transaction. | string | | ||
| | solver_address | The address of the solver (for intent-based bridges). | string | | ||
| | pool_address | The address of the pool (for pool-based and mint-based bridges). | string | | ||
| | bridge_type | The type of bridge (pool-based, mint-based, or intent-based). | string | |
There was a problem hiding this comment.
lets add in a few more columns
log_index
token_address
token_amount
maybe volume_usd to token_amount_usd
There was a problem hiding this comment.
are we doing transaction_hash or transaction_id?
There was a problem hiding this comment.
I've been using transaction_hash elsewhere. There is actually an update to nft/dex ag to that, will submit that.
| List of takers in intent-based bridge protocols. | ||
|
|
||
| | Property | Description | Type | | ||
| |-------------------------|-----------------------------------------------------------|--------| |
There was a problem hiding this comment.
Also, I updated volume_usd to token_amount_usd. Lmk if the descriptions make sense in this case, I am less familiar with intent-based bridges
There was a problem hiding this comment.
I guess I am confused if this is a volume or a balance?
There was a problem hiding this comment.
this should be volume. to get the volume in token amount
There was a problem hiding this comment.
Okay, then I am using volume_amount and volume_usd
| List of takers in intent-based bridge protocols. | ||
|
|
||
| | Property | Description | Type | | ||
| |-------------------------|-----------------------------------------------------------|--------| |
There was a problem hiding this comment.
To clarify, this only covers pool based bridges? I also added token_amount_usd
There was a problem hiding this comment.
not that familiar with all type of bridges , but the goal here is to ensure we have the token amount column for all bridges
There was a problem hiding this comment.
Then I have added token amount and volume amounts and their corresponding USD fields.
- I belv you could have token amounts (or supplied amounts in pools), for pool based bridges
- All bridges have a volume bridged amount
Questions for reviewers