Skip to content

v0.9.1
Compare
Choose a tag to compare
@Bushstar Bushstar released this 13 Mar 12:48
· 19 commits to master since this release
v0.9.1
f6afe2a
This commit was signed with the committer’s verified signature.
Bushstar Peter John Bushnell
GPG key ID: 21E09A54A3615F99
Learn about vigilant mode.

This is the first major update of the OmniFeather which adds Non-Fungible Tokens. This allows for the creation of a smart property where each issued token is unique and can be identified apart from others tokens created in that same smart property, each token is identified by an integer counting from one for the first token. In an issuance a single token or many can be created.

In addition to a unique identifier three additional data fields are added, each allowing up to 255 characters. These three fields are known as grant, issuer and holder data. Grant data is set when the token is issued and cannot be changed. Issuer and holder data is changeable by the issuer and holder respectively, this allows the token to have a state that can change after issuance.

Non-fungible tokens are created using omni_sendissuancemanaged by setting the type to 5 for non-fungible tokens. The tokens themselves are created using omni_sendgrant which is typical behaviour for managed issuance tokens, grant data is also set in this step. Non-fungible tokens can be sent with omni_sendnonfungible and information about them can be obtained with omni_getnonfungibletokens, omni_getnonfungibletokendata and omni_getnonfungibletokenranges. Issuer and holder data is updated with omni_setnonfungibledata.

More information on each of these RPC calls can be found in the link below.

https://github.com/OmniLayer/omnifeather/blob/master/src/omnicore/doc/rpc-api.md

Non-Fungible Tokens Activation

Non-Fungible Tokens are not active on mainnet until block 3,624,000, this is roughly four weeks ahead of launch and should be sometime around 12 April. This feature is already live on testnet and can be tested there in preparation for mainnet launch.

Compatibility with Feathercoin

OmniFeather is based on Feathercoin 0.18.4 and can be used as replacement for Feathercoin. Switching between Omni Core and Feathercoin may be supported. However, it is not advised to upgrade or downgrade to versions other than Feathercoin 0.18.4. When switching to OmniFeather , it may be necessary to reprocess Omni Layer transactions.

OmniFeather Support

If you have any questions or problems with OmniFeather please raise a GitHub issue, send an email or post questions on Telegram linked below.

Website: https://omnifeather.com/
GitHub - https://github.com/FeatherCoin/Feathercoin/issues
Telegram - https://t.me/FeathercoinOfficial
Email - [email protected]

Assets 6
Loading