Skip to content

Releases: DeFiCh/ain

v3.2.5

23 Feb 08:07
@github-actions github-actions
v3.2.5
5be62a9
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v3.2.5

Recommended Upgrade

Upgrade Notes

  • For >= 3.2.0 and <= 3.2.3, reindex is recommended, but optional and can be drop in-upgrade.
    • reindex fixes edge cases where some entries were missing in the outputs of listaccounthistory (fixed in: #1700) and account history related RPC. This does not affect consensus, UTXOs or account balances.
  • For nodes >=3.0.x, one of the following is required:
    • Sync from any of snapshots from the DeFiChain team (below)
    • Any of your own snapshots or data backups before block 2480466 (b41a1d51d80381d3b14be24bc8b2a5524e1c698f5d7cffe5ec4f7b6807ce935a).
  • For all other updates, one of the following is required: a fresh sync, the most recent snapshot.
  • For nodes that are being restored from recent snapshot, as with all updates before: -rescan for the wallet txs and additionally -spv_resync for users who hold BTC. If either isn't used, they may not be shown in the wallet until rescanned/resynced.

Flag Changes

  • Added -dftxworkers=<0/N>: No. of threads in the thread pool for DFTx worker task pool. 0 = automatic.
  • Added -txordering=entrytime/fee/mixed: mixed uses a random selection of entrytime or fee ordering.

Network Snapshot

What's Changed

Full Changelog: v3.2.4...v3.2.5

Contributors

prasannavl, fuxingloh, and 4 other contributors
Assets 8
Loading

v3.2.4

08 Feb 11:15
@github-actions github-actions
v3.2.4
be4bd1f
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v3.2.4

Recommended Upgrade

  • Refactor of history database writers and inclusion of vault collateral changes in vault history
  • Remove left over amounts belonging to a closed vault in loan balances on vault closure
  • Correction to stats in listgovproposalvotes and listgovproposal
  • Support voting by owner or operator address in votegov
  • Fix for staker crash during invalidateblock call
  • Fix for getcustomtx crash when calling on a creategovvoc transaction still in mempool

Upgrade Notes

  • For >= 3.2.0 and <= 3.2.3, reindex is recommended, but is optional and a drop in-upgrade.
    • reindex fixes edge cases where some entries were missing in the outputs of listaccounthistory (fixed in: #1700) and account history related RPC. This does not affect consensus, UTXOs or account balances.
  • For nodes >=3.0.x, one of the following is required:
    • Sync from any of snapshots from the DeFiChain team (below)
    • Any of your own snapshots or data backups before block 2480466 (b41a1d51d80381d3b14be24bc8b2a5524e1c698f5d7cffe5ec4f7b6807ce935a).
  • For all other updates, one of the following is required: a fresh sync, the most recent snapshot.
  • For nodes that are being restored from recent snapshot, as with all updates before: -rescan for the wallet txs and additionally -spv_resync for users who hold BTC. If either isn't used, they may not be shown in the wallet until rescanned/resynced.
  • Users that rely on account, vault or burn history, may want to run their node with -reindex due to a bug fixed in this release that would delete the history of the last six blocks on startup.

RPC Changes

getgovproposal

  • Fixed
    • Argument parsing error.
  • New output fields added
    • votesNo - number of no votes
    • votesNeutral - number of neutral votes
    • votesInvalid - number of invalid votes (votes by ineligible masternodes)
    • feeRedistributionPerVote - DFI redistributed per voter
    • feeRedistributionTotal - total DFI redistributed to voters
    • approvalThreshold - threshold for number of yes votes for proposal to pass

listgovproposalvotes

  • Fixed
    • cycle is set to 1 instead of the current cycle when argument is not set.
    • Argument parsing error.
  • New output field added
    • valid: Validity of vote.
    • Note: This is not finalised until the voting period is completed, results may change over time if active masternodes resign before the completion height.
  • New arguments
    • aggregate: Returns aggregate voting information about one or more proposals.
      • If no proposal ID is sent, voting information for all of the current proposals are returned.
    • valid (default: true): filter results to include only valid or invalid votes.

votegov

  • masternodeId argument now supports owner and operator address.
    • The node will search for masternodes with the provided owner/operator address to vote with.
    • If a masternode ID is provided, behaviour is unchanged.

listvaulthistory

  • PaybackWithCollateral transactions are now listed.

getcustomtx

  • Fixed crash when decoding unconfirmed CreateVoc transactions.

What's Changed

  • Move CHistoryWriter into CCustomCSView by @Bushstar in #1700
  • Track Add/SubVaultCollateral in vault history by @Bushstar in #1715
  • Add more voting info in getgovproposal rpc by @Mixa84 in #1729
  • Change first parameter of listgovproposals and listgovproposalvotes to be string and parsed as JSON in rpc by @Mixa84 in #1732
  • rpc: votegov: Add support for owner and operator address by @DocteurPing in #1717
  • Addapt fee redistribution test to current situation by @Mixa84 in #1728
  • Remove positive amount on close vault by @Bushstar in #1712
  • Display vote validity in listgovproposals and add validity filter by @shohamc1 in #1725
  • Display aggregate vote stats in listgovproposalvotes by @shohamc1 in #1714
  • Add checkpoints to testnet/devnet by @Bushstar in #1738
  • Fix getcustomtx crash on mempool transaction by @Bushstar in #1742
  • Display vote validity in listgovproposals and add validity filter by @shohamc1 in #1740
  • Fix staker crash on invalidateblock by @Bushstar in #1741
  • v3.2.4 by @Bushstar in #1745

Full Changelog: v3.2.3...v3.2.4

Contributors

Bushstar, shohamc1, and 2 other contributors
Assets 8
Loading

v3.2.3

03 Feb 12:26
@github-actions github-actions
v3.2.3
300e24f
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v3.2.3

Optional Upgrade

  • An optional upgrade to resolve a performance regression in the node: https://github.com/DeFiCh/ain/issues/1730
  • Disables neutral votes from being set through RPC due to prevent accidental neutral votes temporarily until #1704 is fixed.
  • listgovproposalvotes default values now work as expected to show current cycle instead of the last one.

Upgrade Notes

  • For >= 3.2.0, it is a drop in-upgrade.
  • For nodes >=3.0.x, one of the following is required:
    • Sync from any of snapshots from the DeFiChain team (below)
    • Any of your own snapshots or data backups before block 2480466 (b41a1d51d80381d3b14be24bc8b2a5524e1c698f5d7cffe5ec4f7b6807ce935a).
  • For all other updates, one of the following is required: a fresh sync, the most recent snapshot.
  • For nodes that are being restored from recent snapshot, as with all updates before: -rescan for the wallet txs and additionally -spv_resync for users who hold BTC. If either isn't used, they may not be shown in the wallet until rescanned/resynced.

Network Snapshot

What's Changed

Full Changelog: v3.2.2...v3.3.0

Contributors

prasannavl, Bushstar, and 3 other contributors
Assets 8
Loading

v3.2.2

19 Jan 02:52
@github-actions github-actions
v3.2.2
314cf76
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v3.2.2

Optional Upgrade

  • RPCs with fixes and improvements:
    • listaccounthistory: Support for pagination
    • listgovproposals: Multiple fixes and improvements
    • accouthistorycount: Adds txtypes support for accepting multiple types
  • Flags:
    • -backupwallet: Enables automatic wallet backups. This feature is currently experimental and is disabled by default as large wallets can block the validation process during the automatic backup.
    • -leveldbchecksum: Controls the leveldb check sum behaviour and allows bypass to favour faster validations for testing and on non masternodes.
    • -devnet: Enables bootstrapping first iteration of the new network devnet

Upgrade Notes

  • For >= 3.2.0, it is a drop in-upgrade.
  • For nodes >=3.0.x, one of the following is required:
    • Sync from any of snapshots from the DeFiChain team (below)
    • Any of your own snapshots or data backups before block 2480466 (b41a1d51d80381d3b14be24bc8b2a5524e1c698f5d7cffe5ec4f7b6807ce935a).
  • For all other updates, one of the following is required: a fresh sync, the most recent snapshot.
  • For nodes that are being restored from recent snapshot, as with all updates before: -rescan for the wallet txs and additionally -spv_resync for users who hold BTC. If either isn't used, they may not be shown in the wallet until rescanned/resynced.

Network Snapshot

Changes

Full Changelog: v3.2.1...v3.2.2

Contributors

Bushstar, shohamc1, and 4 other contributors
Assets 8
Loading

v3.2.1

05 Jan 09:09
@github-actions github-actions
v3.2.1
067fc62
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v3.2.1

Important Information

During one of our pre-hardfork checks, we identified that some of the recent snapshots before Jan 10, 2023 provided by the following sources were created by nodes that were updated incorrectly, resulting in inconsistent data:

All of the incorrect snapshots have now been removed from the above sources, regenerated and verified to be correct as of Jan 11, 2023.
Freshly synced nodes with 3.1.x nodes are unaffected and are ready for the Grand Central Epilogue network upgrade. For those that have used any of the above sources to bootstrap the network, please update your nodes from the same sources again.

Recent verified snapshots:

Optional Upgrade

  • Additional filters and pagination for on-chain governance related RPCs
  • Optional support for time based TX ordering miner policy
  • SPV related fixes that hangs the shutdown process under certain conditions
  • Accounting fixes for getburninfo related to BurnTokenTx

Upgrade Notes

  • For >= 3.2.0, it is a drop in-upgrade.
  • For nodes >=3.0.x, one of the following is required:
    • Sync from any of snapshots from the DeFiChain team (below)
    • Any of your own snapshots or data backups before block 2480466 (b41a1d51d80381d3b14be24bc8b2a5524e1c698f5d7cffe5ec4f7b6807ce935a).
  • For all other updates, one of the following is required: a fresh sync, the most recent snapshot.
  • For nodes that are being restored from recent snapshot, as with all updates before: -rescan for the wallet txs and additionally -spv_resync for users who hold BTC. If either isn't used, they may not be shown in the wallet until rescanned/resynced.

Changes

Full Changelog: v3.2.0...v3.2.1

Contributors

Bushstar, shohamc1, and 3 other contributors
Assets 8
Loading

v3.2.0

27 Dec 11:20
@Jouzo Jouzo
v3.2.0
16ea458
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v3.2.0

Mandatory Upgrade 🎅

This is a mandatory update for the upcoming Grand Central Epilogue chain upgrade. It contains key upgrades for the protocol.
Grand Central Epilogue upgrade is set for block 2574000 (approx. ETA Jan 10th, 2023. UTC) on mainnet.

Update of mainnet node to v3.2 before the chain upgrade block is REQUIRED.

Important Information

During one of our pre-hardfork checks, we identified that some of the recent snapshots before Jan 10, 2023 provided by the following sources were created by nodes that were updated incorrectly, resulting in inconsistent data:

All of the incorrect snapshots have now been removed from the above sources, regenerated and verified to be correct as of Jan 11, 2023.
Freshly synced nodes with 3.1.x nodes are unaffected and are ready for the Grand Central Epilogue network upgrade. For those that have used any of the above sources to bootstrap the network, please update your nodes from the same sources again.

Recent verified snapshots:

Upgrade Notes

  • For >= 3.1.0, it is a drop in-upgrade.
  • For nodes >=3.0.x, one of the following is required:
    • Sync from any of snapshots from the DeFiChain team (below)
    • Any of your own snapshots or data backups before block 2480466 (b41a1d51d80381d3b14be24bc8b2a5524e1c698f5d7cffe5ec4f7b6807ce935a).
    • Fresh sync.
  • For nodes that are being restored from recent snapshot, as with all updates before: -rescan for the wallet txs and additionally -spv_resync for users who hold BTC. If either isn't used, they may not be shown in the wallet until rescanned/resynced.
  • For other nodes, one of the following is required: a fresh sync, the most recent snapshot.

Key highlights

This is planned extension upgrade to 3.1.x that fixes improves protocol stability to ensure the network is ready for enabling the rest of Grand Central features.

Network Snapshot

Merry Christmas! 🎄

Changes

Full Changelog: v3.1.1...v3.2.0

Contributors

prasannavl, Bushstar, and 2 other contributors
Assets 8
Loading

v3.1.1

09 Dec 01:21
@github-actions github-actions
v3.1.1
4605cf4
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v3.1.1

Recommended Upgrade

This is a recommended update that fixes a crash in 3.0.x that gets the chain to be stuck on valid TXs.

Important Info:

  • 3.0.x nodes continue to be supported in the network.
  • There is no requirement to upgrade to be a part of the network either to stake or validate.
  • The key purpose of v3.1.1 was to align the network quickly and prevent network splits in the interim and synchronise the network.
  • The bug was caused due to a missing revert in the implementation for DeFiCh/dfips#228. This feature has now been turned off is not expected to be enabled until the next planned network upgrade.

Upgrade Notes

  • For nodes >=3.1.0, it's a drop-in upgrade.
  • For nodes >=3.0.x, one of the following is required:
    • Sync from any of snapshots from the DeFiChain team (below)
    • Any of your own snapshots or data backups before block 2480466 (b41a1d51d80381d3b14be24bc8b2a5524e1c698f5d7cffe5ec4f7b6807ce935a).
    • Fresh sync.
  • For nodes that are being restored from recent snapshot, as with all updates before: -rescan for the wallet txs and additionally -spv_resync for users who hold BTC. If either isn't used, they may not be shown in the wallet until rescanned/resynced.
  • For other nodes, one of the following is required: a fresh sync, the most recent snapshot.

Network Snapshot

Network state of mainnet of the current longest chain from https://defiscan.live:

2480535: 588c270f7c3bcadf355982f395da39caddc8b0018e5c3bd3e2cdfc76ddf9cb24
2480575: c9166f806ff39b1dba64fb08ccadc16093315455cd7f7109a170030772706313
2480618: 25017f40f3035e80e9d0748cedac78112b9338dbae01d6a862058a17343924ce

Changes

  • Version v3.1.1 (#1642)
  • Add undo in ReversGeneralCoinbaseTx() (#1641)

Misc

Tips:

  • To check if you're on the right chain:
defi-cli getblockhash 2480535
  • To get on the right chain if you aren't:
$ defi-cli invalidateblock $(defi-cli getblockhash 2480535)
$ defi-cli clearbanned
$ defi-cli reconsiderblock 588c270f7c3bcadf355982f395da39caddc8b0018e5c3bd3e2cdfc76ddf9cb24
Assets 8
Loading

v3.0.1 - Grand Central

28 Nov 08:41
@github-actions github-actions
v3.0.1
8d233a4
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v3.0.1 - Grand Central

Mandatory Upgrade

This is a mandatory update for the upcoming Grand Central chain upgrade. It contains key upgrades for the protocol.
Grand Central upgrade is set for block 2479000 (approx. ETA Dec 8th, 2022. UTC) on mainnet.

Update of mainnet node to v3.0.x before the chain upgrade block is REQUIRED.

Upgrade Notes

  • For nodes >= 2.11.1, reindex is recommended but optional.
  • What works without reindex: Consensus, fund related contracts are 100% compatible and reindex isn't required.
  • What requires reindex: bug fixes for statistical information like getburninfo and live attributes. (listgov attrs). Without reindex, they'll continue to follow older accounting semantics.
  • For nodes that are being restored from recent snapshot, as with all updates before: -rescan for the wallet txs and additionally -spv_resync for users who hold BTC. If either isn't used, they may not be shown in the wallet until rescanned/resynced.
  • For other nodes, one of the following is required: a fresh sync, the most recent snapshot.

Key Highlights

  • On-chain governance
  • Token consortium framework
  • Support for masternode parameter updates (owner, operator, reward address)
  • Pool commission and reward fixes

Testnet Info

The following are informational updates that apply only for development on testnet:

  • Testnet has been rolled back to 1366000 prior to this release.
  • Reference blockhash of testnet 1366000: 3b353a200ebee7aec49f5acc41d7711ceea7bfa63474d00fcff674a859aa9e13
  • Note: Same upgrade notes as mainnet apply to testnet. Please reindex / restore as necessary.

Note: Certain test related infrastructure components (like defiscan.live) could take a while to reflect this change, due to the re-indexing constraints on the specific applications.

Testnet rollback tips (if needed):

$ defi-cli -testnet invalidateblock $(defi-cli -testnet getblockhash 1366000)
$ defi-cli -testnet clearbanned
$ defi-cli -testnet reconsiderblock 3b353a200ebee7aec49f5acc41d7711ceea7bfa63474d00fcff674a859aa9e13

What's Changed

Read more

Contributors

uzyn, prasannavl, and 5 other contributors
Assets 8
Loading

v2.11.1

16 Sep 07:56
@Bushstar Bushstar
v2.11.1
17c7d00
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v2.11.1

Mandatory Upgrade

This is a mandatory update for the upcoming Fort Canning Epilogue chain upgrade. It contains key upgrades for the protocol.
Fort Canning Epilogue upgrade is set for block 2257500 (approx. ETA Sep 22, 2022 UTC) on mainnet.

Update of mainnet node to v2.11.1 before the chain upgrade block is REQUIRED.

Upgrade Notes

  • For nodes >= 2.9.1, this is a drop in upgrade. No reindex required.
  • For nodes that are being restored from recent snapshot, as with all updates before: -rescan for the wallet txs and additionally -spv_resync for users who hold BTC. If either isn't used, they may not be shown in the wallet until rescanned/resynced.
  • For other nodes, one of the following is required: a fresh sync, the most recent snapshot.

What’s Changed

🚀 Features

  • Update DFI DUSD vault collateral requirement rules @hidiego (#1450)
  • Allow payback of DUSD with vault's collateral @Jouzo (#1451)
  • Allow higher collateral factor @Bushstar (#1452)
  • Add FortCanningEpilogue fork @Bushstar (#1449)

🐛 Bug Fixes

🧰 Maintenance

How to run?

Download and untar the relevant version to your operating system, run bin/defid or bin/defid.exe to start a DeFi Blockchain daemon. The client (CLI) can be found at bin/defi-cli or bin/defi-cli.exe.

DeFi App (GUI) users

If you are running the desktop DeFi App, you do not have to manually update the underlying node as the app will handle it. Check https://github.com/DeFiCh/app/releases for the latest releases.

Contributors

prasannavl, Bushstar, and 5 other contributors
Assets 8
Loading

v2.10.0 - Fort Canning Great World

30 Aug 23:43
@prasannavl prasannavl
v2.10.0
920a70c
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v2.10.0 - Fort Canning Great World

Mandatory Upgrade

This is a mandatory update for the upcoming Fort Canning Great World chain upgrade. It contains key upgrades for the protocol.
Fort Canning Great World upgrade is set for block 2212000 (approx. ETA Sep 6, 2022 UTC) on mainnet.

Update of mainnet node to v2.10.0 before the chain upgrade block is REQUIRED.

Upgrade Notes

  • For nodes >= 2.9.1, this is a drop in upgrade. No reindex required.
  • For nodes that are being restored from recent snapshot, as with all updates before: -rescan for the wallet txs and additionally -spv_resync for users who hold BTC. If either isn't used, they may not be shown in the wallet until rescanned/resynced.
  • For other nodes, one of the following is required: a fresh sync, the most recent snapshot.

Key Focus

  • Negative interest rate support

What’s Changed

🚀 Features

🐛 Bug Fixes

  • Zero interest is not negative @Bushstar (#1431)
  • Add overflow check on interest rates @prasannavl (#1432)
  • Fix clearmempool to clear wallet TX and refactor test rollbacks @hidiego (#1428)
  • show debug log on success or failure @mambisi (#1426)
  • Explicitly specify Param type in CAmount export @Bushstar (#1418)
  • Fix jellyfish test job commands @Jouzo (#1425)
  • Log "kernel found" without debug flag @Jouzo (#1420)
  • Fix -stop-block and -interrupt-block crashing when used on empty -datadir @Jouzo (#1416)

🧰 Maintenance

How to run?

Download and untar the relevant version to your operating system, run bin/defid or bin/defid.exe to start a DeFi Blockchain daemon. The client (CLI) can be found at bin/defi-cli or bin/defi-cli.exe.

DeFi App (GUI) users

If you are running the desktop DeFi App, you do not have to manually update the underlying node as the app will handle it. Check https://github.com/DeFiCh/app/releases for the latest releases.

Contributors

prasannavl, Bushstar, and 3 other contributors
Assets 8
Loading