Create base code for a new transaction type or refractor current transaction structure to produce
Transaction type:
new_asset: this transaction type is used when a new asset name is registered
new_asset extraPayload structure:
Name: 1-128 chars [a-zA-Z0-9] and space
updatable: bool - if true this asset meta can be modified using assetTx update process (see Assets issue # 5). Otherwise these asset metadata can’t be updated.
Is_unique: true if this is asset is unique it has an identity per token (NFT flag)
Decimal point: has to be 0 if is_unique is true.
referenceHash: hash of the underlying physical or digital assets, IPFS hash can be used here.
Distribution:
Type: unit8 - possible types are manual, coinbase, address, and schedule
targetAddress: address to be issued to when asset issue transaction is created. If type is address then whenever a transaction occurred to this address then distribution occurs. If type is scheduled this is the address where assets will be issued per schedule.
issueFrequency: uint8 - mint specific amount of token every x blocks.
Amount: CAmount - amount to distribute each time if type is not manual.
ownerAddress: wallet address that this asset is owned by. Only key holder of this address will be able to mint new tokens
collateralAddress: wallet address where collateral for minting asset fee will be in if type is not manual
Burns: similar to distribution but send asset to a burn address or future lock it forever
A) Make use of OP_ASSET_ID (see Assets #2 issue)
B) ensure full backwards and forwards compatibility post changes. Including syncs from scratch and continuation post shutdown
C) Create appropriate unit and possibly fuzz or other tests to ensure compliance and avoid unforeseen issues.
Bigpiggy01
commented
7 months ago
Create base code for a new transaction type or refractor current transaction structure to produce
Transaction type:
Name: 1-128 chars [a-zA-Z0-9] and space
updatable: bool - if true this asset meta can be modified using assetTx update process (see Assets issue # 5). Otherwise these asset metadata can’t be updated.
Is_unique: true if this is asset is unique it has an identity per token (NFT flag)
Decimal point: has to be 0 if is_unique is true.
referenceHash: hash of the underlying physical or digital assets, IPFS hash can be used here.
Distribution:
Type: unit8 - possible types are manual, coinbase, address, and schedule
targetAddress: address to be issued to when asset issue transaction is created. If type is address then whenever a transaction occurred to this address then distribution occurs. If type is scheduled this is the address where assets will be issued per schedule.
issueFrequency: uint8 - mint specific amount of token every x blocks.
Amount: CAmount - amount to distribute each time if type is not manual.
ownerAddress: wallet address that this asset is owned by. Only key holder of this address will be able to mint new tokens
collateralAddress: wallet address where collateral for minting asset fee will be in if type is not manual
Burns: similar to distribution but send asset to a burn address or future lock it forever
A) Make use of OP_ASSET_ID (see Assets #2 issue)
B) ensure full backwards and forwards compatibility post changes. Including syncs from scratch and continuation post shutdown
C) Create appropriate unit and possibly fuzz or other tests to ensure compliance and avoid unforeseen issues.