digibyte-core/digiassetsd

RESTful web server for DigiAsset protocol operations, implemented in Node.js.

digiassetsd's Issues

sendasset no way to define change

quantum computers are coming. As long as funds are never deposited into an address that has sent funds DigiByte is quantum secure. Unfortunetly the asset server has no way to define the change address for funds used to send an asset. As a result all funds and assets involved with the original sending address are at risk. A field to define where to send change funds needs to be available.

IPFS for metadata storage

Opening this to get some thoughts on integrating IPFS as a metadata solution for digiassets.

Initial thoughts are that we could use the files CID instead of the SHA256 torrent hash, this would require multisig addresses be used as the current maximum length of a CID is 64 bytes. As SHA256 torrent hash is already using this method we may also need some way for the asset protocol to distinguish between SHA256 torrent metadata and IPFS CID.

Metadata stored on the IPFS network should be easily shared between metadata nodes. Enabling both this new type of decentralized storage while retaining current functionality is important as there will be entities that wish to host and secure their own metadata.

https://docs.ipfs.io/introduction/overview/
https://github.com/DigiByte-Core/DigiAssets-Protocol-Specifications/wiki/DigiAsset%20Scheme#blockchain-data-recording-logic