go-bitsong
go-bitsong copied to clipboard
bitsongofficial
:rocket: Official BitSong Blockchain Implementation in Go
In the `launchpad` module, the ability to mint is available inside a time interval. Its boundaries are `go_live_date` and `end_timestamp`, in lines 22 and 24 https://github.com/bitsongofficial/go-bitsong/blob/afcba32b4f1dfc1a6db7140b01d17eec347daf99/proto/bitsong/launchpad/launchpad.proto#L12-L41 This approach Is different...
In some usage of the `nft` technology, it could be very useful to provide non-transferable nft. This kind of token, once they are minted, cannot be transferred to another owner....
In the `marketplace` module, there is a method that processes the shares of the royalties for "not-primary" sales. The `ProcessRoyalties` method https://github.com/bitsongofficial/go-bitsong/blob/84691c819214a1f9b9dd844ea2b49b7ccc8ece1b/x/marketplace/keeper/royalties.go#L8-L37 Send coins to the creators, but it does...
In the `nft` module, which is the difference between a _normal_ NFT (MasterEdition equal to nil) and an NFT with MasterEdition and `MaxSupply` = 1? I think the two represent...
In the `nft` module, inside the methods of the `msg_server`, we should improve the validations. In particular, we should include validation on: - `CreateCollection` method: on data of the collection...
In the `nft` module, the fees spent to `issue` a new NFT are sent to the module and next they are **burned**. Instead, we could think to move them to...
In the `nft` module, there is the `nft/types/msgs_test.go` file, which should contain the tests for the messages. These tests are missing ATM and we should implement them.
In the `nft` module, ATM no simulation is provided. We should add them.
In the `nft` module, ATM the `UpdateMetadataAuthority` method is able to modify the `MetadataAuthority` even if the metadata is mutable no more (`isMutable` = false). The method is also involved...
Metadata
Owner
Metadata
:rocket: Official BitSong Blockchain Implementation in Go