Releases: OmniLayer/omnifeather
v0.9.2
Changes in 0.9.2
- Remove hard coded property ID 3 Feather to improve compatibility with external libs. Properties will only be created using OmniLayer TXs.
- Free NFT DB at shutdown.
- Default the NFT debug log to off.
- omni_getnonfungibletokendata update to show a range of tokens.
- Use state files to recover state on start up if watermark not in block index, avoids full reparse of OmniLayer in such situations.
- When calculating Omni TX class type include opcodes, thanks to Regan for reporting this issue.
- Show Omni version in Qt and CLI version info.
- omni_getnonfungibletokens can now show all NFTs on an address, property ID is now an optional argument.
NOTE: Due to the removal of the hard coded property ID 3 the database will be wiped and a full reparse of all OmniLayer transaction will be performed on start up. This process may take several hours to complete.
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 - admin@feathercoin.com
v0.9.1
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 - admin@feathercoin.com
OmniFeather v0.9.0
This is the first release of the OmniFeather which adds OmniLayer functionality to the Feathercoin blockchain. This allows for the creation of additional assets on the Feathercoin blockchain other than the native feathercoin. Assets can be either managed or have a fixed supply, can be introduced via crowdsale and exchanged via an decentralised exchange built into the OmniFeather protocol.
For a full list of commands please refer to the documentation below. A website will soon be available outlining some of the basic functions of OmniFeather, the URL will be posted here and announced via social media when available.
https://github.com/OmniLayer/omnifeather/blob/master/src/omnicore/doc/rpc-api.md
This version is marked as v0.9.0 as that is the version of Omni Core, the Bitcoin based reference implementation of OmniLayer, that has been used for Feathercoin and is currently the latest available version. To see the release history and changes for Omni Core check the link below.
https://github.com/OmniLayer/omnicore/releases
OmniLayer Activation
OmniLayer functionality is not available on mainnet until activation block 3,454,000 is reached approximately on the 9th of December. This gives users time to experiment with OmniFeather using regtest and testnet which both parse OmniLayer transactions after block 101.
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.
GitHub - https://github.com/FeatherCoin/Feathercoin/issues
Telegram - https://t.me/FeathercoinOfficial
Email - admin@feathercoin.com