Releases: fioprotocol/fio.contracts
Release Candidate - FIO v2.8.0-rc1
Enhancements and Updates
This release is comprised of 2 Features, FIP-17 and FIP-41.
FIP-17a FIO Token Wrapping. Contracts specific changes include the addition of several actions including wraptokens, wrap_fio_tokens, unwraptokens, regoracle, unregoracle, and setoraclefee.
FIP-41 Enable token locking to existing accounts. This FIP removes the restriction that transfer_locked_tokens can only transfer tokens to a FIO Public Key which has not yet been established as an account. This FIP modifies one action, trnsloctoks, and adds one action, clrgenlocked.
Refer to the FIO Release Notes for additional information on any related FIO core changes,
What's Changed
FIO Token Wrapping Development
FIO Domain Wrapping Development
Release - FIO Contracts v2.7.1
Bug Fixes
(#248) Fixes 2 bugs in the fio.escrow contract. The first bug is related to TPID. The second bug is related to checking if a domainsale was valid when purchasing.
What's Changed
- update errant error details (into develop branch) by @ericbutz in #205
- Feature/fip 21 staking r2 6 x 11102021 > develop by @ericbutz in #207
- Xferdomain update by @adsorptionenthalpy in #210
- newfundsreq/recordobt increase max content by @adsorptionenthalpy in #118
- Bump up ram per NFT added by @adsorptionenthalpy in #203
- FIP-33 ( Add $ support on chain name validation ) by @0xCasey in #212
- [FIP-22] Retire action by @adsorptionenthalpy in #208
- change token_id supported length to 128 by @adsorptionenthalpy in #217
- FIP-32 / FIP-34 ( Increased content on newfundsreq and recordobt ) by @0xCasey in #215
- Merge Release/2.6.x to develop by @ericbutz in #219
- fio.escrow updates by @tvl83 in #197
- Rebase develop with master ( v 2.6.1 ) by @0xCasey in #225
- FIP-22 Retire fixes by @adsorptionenthalpy in #226
- Add owner lookup to allow for multiple escrow marketplaces by @0xCasey in #228
- retire fixes testing (release/2.7.x) by @adsorptionenthalpy in #231
- Escrow ram adjust by @tvl83 in #233
- Update cmake and readme to 2.7.0 by @ericbutz in #234
- Release 2.7.0 to master (Release/2.7.x -> master) by @0xCasey in #243
- Bugfix/fioescrow by @tvl83 in #248
New Contributors
Full Changelog: v2.6.1...v2.7.1
Contributors
Assets 2
Release Candidate - FIO Contracts v2.7.1-rc1
Bug Fixes
(#248) Fixes 2 bugs in the fio.escrow contract. First bug is related to TPID. The second bug is related to checking if a domainsale was valid when purchasing.
Release - FIO Contracts v2.7.0
Enhancements and Updates
(#208) FIP-22 Retire FIO Tokens. Modifies the retire action to allow users to burn their own tokens.
(#197) FIP-26 New Domain Marketplace contract. Deploys a new fio.escrow system contract. This contract creates four new actions: listdomain, cxlistdomain, buydomain, and setmrkplcfg to support the Domain Marketplace application. The marketplace enables users to buy and sell FIO Domains. Users interact with the frontend website to view and place domains up for sale. The frontend interacts with the fio.escrow system contract to facilitate transactions between users who buy and sell domains.
(#215) FIP-32 Allow unlimited size of content parameter in New Funds Request. This update modifies the newfundsreq action to allow for an unlimited size of the content parameter to accommodate Lightning Network invoices or any other data that FIO Protocol users would want to include in FIO Request. The newfundsreq fee is assessed based on the size of the request.
(#212) FIP-33 Allow $ in chain/token codes. Updates the addaddress and remaddress actions to allow $ (dollar sign) as the token code or chain code. This provides support for chains (e.g. Ethereum, Binance SmartChain) that allow "$" as a token code.
(#215) FIP-34 Allow unlimited size of content parameter in Record OBT Data. This update modifies the recordobt action to allow for an unlimited size of the content parameter. The recordobt fee is assessed based on the size of the request.
(#217) FIP-35 Increase NFT token_id size. Updates the addnft action to allow token_id to be max 128 characters, up from 64.
What's Changed
- update errant error details (into develop branch) by @ericbutz in #205
- Feature/fip 21 staking r2 6 x 11102021 > develop by @ericbutz in #207
- Xferdomain update by @adsorptionenthalpy in #210
- newfundsreq/recordobt increase max content by @adsorptionenthalpy in #118
- Bump up ram per NFT added by @adsorptionenthalpy in #203
- FIP-33 ( Add $ support on chain name validation ) by @0xCasey in #212
- [FIP-22] Retire action by @adsorptionenthalpy in #208
- change token_id supported length to 128 by @adsorptionenthalpy in #217
- FIP-32 / FIP-34 ( Increased content on newfundsreq and recordobt ) by @0xCasey in #215
- Merge Release/2.6.x to develop by @ericbutz in #219
- fio.escrow updates by @tvl83 in #197
- Rebase develop with master ( v 2.6.1 ) by @0xCasey in #225
- FIP-22 Retire fixes by @adsorptionenthalpy in #226
- Add owner lookup to allow for multiple escrow marketplaces by @0xCasey in #228
- retire fixes testing (release/2.7.x) by @adsorptionenthalpy in #231
- Escrow ram adjust by @tvl83 in #233
- Update cmake and readme to 2.7.0 by @ericbutz in #234
- Release 2.7.0 to master (Release/2.7.x -> master) by @0xCasey in #243
New Contributors
Full Changelog: v2.6.1...v2.7.0
Contributors
Assets 2
Release Candidate - FIO Contracts v2.7.0-rc1
Enhancements and Updates
(#208) FIP-22 Retire FIO Tokens. Modifies the retire action to allow users to burn their own tokens.
(#197) FIP-26 New Domain Marketplace contract. Deploys a new fio.escrow system contract. This contract creates four new actions: listdomain, cxlistdomain, buydomain, and setmrkplcfg to support the Domain Marketplace application. The marketplace enables users to buy and sell FIO Domains. Users interact with the frontend website to view and place domains up for sale. The frontend interacts with the fio.escrow system contract to facilitate transactions between users who buy and sell domains.
(#215) FIP-32 Allow unlimited size of content parameter in New Funds Request. This update modifies the newfundsreq action to allow for an unlimited size of the content parameter to accommodate Lightning Network invoices or any other data that FIO Protocol users would want to include in FIO Request. The newfundsreq fee is assessed based on the size of the request.
(#212) FIP-33 Allow $ in chain/token codes. Updates the addaddress and remaddress actions to allow $ (dollar sign) as the token code or chain code. This provides support for chains (e.g. Ethereum, Binance SmartChain) that allow "$" as a token code.
(#215) FIP-34 Allow unlimited size of content parameter in Record OBT Data. This update modifies the recordobt action to allow for an unlimited size of the content parameter. The recordobt fee is assessed based on the size of the request.
(#217) FIP-35 Increase NFT token_id size. Updates the addnft action to allow token_id to be max 128 characters, up from 64.
Release - FIO Contracts v2.6.1
Bug Fixes
(#222) Insufficient funds error when collecting fees from locked tokens
Release - FIO Contracts v2.6.0
Enhancements and Updates
(#124) FIP-21 FIO Staking. Extends FIO Protocol to enable FIO tokens to be staked. Users can stake any available FIO Token amount in their account at any point in time. To stake, the account has to be voting for at least 1 BP or proxying/auto-proxying. The FIO Tokens do not actually leave the user's account, but are instead "locked" and cannot be spent until unstaked.
General lock tokens updated. As part of FIP-21 it was discovered that existing FIP-6 locking functionality, which uses percentage for each lock period, will not be able to sufficiently support unstaking locking required by this FIP. As a result, and to make locks more robust for future applications, this FIP modifies locking to accept SUFs instead of percentages when specifying period amount. Additional updates to locks:
- Any existing general locks will be deleted. New locks will have to be created.
- The number of lock periods is limited to a maximum of 50 locks periods.
Release Candidate - FIO Contracts v2.6.0-rc3
Merge pull request #216 from fioprotocol/feature/remove-expired-addre…
Release Candidate - FIO Contracts v2.6.0-rc2
Enhancements and Updates
(#124) FIP-21 FIO Staking. Extends FIO Protocol to enable FIO tokens to be staked. Users can stake any available FIO Token amount in their account at any point in time. To stake, the account has to be voting for at least 1 BP or proxying/auto-proxying. The FIO Tokens do not actually leave the user's account, but are instead "locked" and cannot be spent until unstaked.
General lock tokens updated. As part of FIP-21 it was discovered that existing FIP-6 locking functionality, which uses percentage for each lock period, will not be able to sufficiently support unstaking locking required by this FIP. As a result, and to make locks more robust for future applications, this FIP modifies locking to accept SUFs instead of percentages when specifying period amount. Additional updates to locks:
- Any existing general locks will be deleted. New locks will have to be created.
- The number of lock periods is limited to a maximum of 50 locks periods.
Release - FIO Contracts v2.5.0
Enhancements and Updates
(#146) FIP-27 NFT Signatures. Extends FIO Protocol to enable NFTs to be mapped to a FIO Address. It will allow anyone to see which FIO Address has mapped ("signed") a particular NFT and if it is a FIO Address they trust, they can also trust the NFT.
(#177) FIP-31 Eliminate FIO Address Expiration. Eliminates the concept of expiration of FIO Addresses. FIO Addresses will now be valid and functional indefinitely and will never be burned. Users will still need to purchase bundled transactions or pay-per-call to continue to call actions on the FIO Address.
(#183) burnnfts admin endpoint. Enables the burning of large numbers of NFTs. When a FIO Address is burned, it is added to a queue. burnnfts accesses this queue to determine which NFTs to burn. While this call can be made by any user, it is expected that FIO block producers will regularly call it to ensure the NFT burn queue remains empty.
Bug Fixes
(#174) Burnexpired not burning expired domains. Fixes bug that was preventing burnexpired from burning domains when there were large blocks of expired and non-expired domains.
(#192) Removal of binary extensions from the fio.address contract.