Skip to content

Conversation

sucildossj
Copy link

Included following changes

scantxoutset rpc changes for asset
listunspent rpc changes for asset
create premium transaction rpc
send asset transaction rpc
send pegout transaction rpc

@sucildossj sucildossj requested a review from jasonribble October 1, 2025 14:32
Copy link

@jasonribble jasonribble left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Feel free to keep formatting from upstream to reduce merge conflict in the future

Copy link

@jasonribble jasonribble left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The CAsset in the outpoint looks looks good

@sucildossj
Copy link
Author

sucildossj commented Oct 9, 2025

The CAsset in the outpoint looks looks good
Currently, I’m changing the data type to a buffer that holds 8 bytes (int64_t) for the block number and 2 bytes (int16_t) for the asset number within the block. Each block can have only 256 new assets, with asset IDs ranging from 001 to 256. We need to filter the block template to allow only 256 assets per block and ensure this rule is validated in the consensus layer as well. @jasonribble

@sucildossj
Copy link
Author

Additionally, if an asset creation transaction is still in the mempool, we need to wait until it is confirmed before allowing any transfers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants