Releases: atomicals/atomicals-electrumx
Atomicals ElectrumX Node v1.4.0
The main purpose of this release is to add the TX detail RPC calls and to improve the error handling, and various bugs fixes.
This release requires reindex.
Changes:
Change transaction struct [Change inputs output to list]
#151
Use fixed merkletools
#149
Adds RocksDB binding dependencies
#152
Fix transaction content format before returned to the cal
#154
Add python-dotenv to automatically load environments
#155
Clear all history caches when block height changed
#159
Improve subscribe headers
#157
Hide candidates when no status
#140
Returns parents for all sub-item
#160
Returns parents for all sub-item
#160
Support Daemon proxy
#162
Fix transaction return error atomical_id
#163
Avoid parent container KeyError
#167
Produce readable AtomicalsValidationError
#158
Configurable LOG_LEVEL with .env
#171
Atomicals ElectrumX Node v1.3.9.1
The purpose of this release is to fix a bug with non-leading candidates and incorrectly labelling the candidates which could confuse users and discourage them from paying (when in fact they are the leading candidates). There are additional stability and improved status tests added for future stability.
Changes:
🐛 Fix non-leading candidates payment status
#98
Add basic subrealm and dmitem candidate status tests
#116
Continue to enhance subrealm and dmitem status test coverage
#117
Fix RPC call to query by find_subrealms to correctly return the subrealms and be able to filter by prefix
#118
Add status for when a subname such as subrealm or dmitem cannot ever be valid because an earlier candidate made a payment
#121
[Improvement]Log file can not be rotate daily without restarting
#119
⚡️ Improve get_subname_request_candidate_status
#122
Fix exception in the name rpc calls
#124
Add the subject to the db index name search
#125
Fix key error when getting subname status
#127
Rename RPC response correctly to return entity type (as it existed before the refactor)
#128
Atomicals ElectrumX Node v1.3.9.0
The purpose of this release is to resolve the issue of perpetual bitwork not being accepted for the "next upcoming" Bitwork. This change makes it so that strictly more Bitwork is now also accepted despite the current Bitwork being lower.
Changes:
Allow perpetual dft mining to correctly accept the next bitwork
#110
fix perpetual holder error and constant import
#111
Atomicals ElectrumX Node v1.3.8.4
This is the correct release for perpetual mining tokens. Disregard other versions of v1.3.8.x and use this one only.
Changes (Total):
Allow set bri and bci to 0
#107
Do not force increment
#106
Ensure bci and bri are between 1 and 64 and Fix error on incorrect hex for bv
#102
Add max_mints_global for perpetual tokens
#103
Fix bug to not well defined bcs or brs
#100
fix #92 get wrong ft/nft balance.
#99
Correctly deference mint_mode and default to 'fixed' when not set
#94
bugfix: fix env and import base64
#97
Fix http session for dft mint entries
#96
Perpetual Toking Mining ARC20 with Bitwork
#93
add ENABLE_RATE_LIMIT for customization
#88
Use a fixed pylru with to avoid key deletion exceptions
#81
feature: support http protocol
#58
Atomicals ElectrumX Node v1.3.8.3
Disregard other versions of previous v1.3.8.x and use this one only.
Changes (Total):
Ensure bci and bri are between 1 and 64 and Fix error on incorrect hex for bv
#102
Add max_mints_global for perpetual tokens
#103
Fix bug to not well defined bcs or brs
#100
fix #92 get wrong ft/nft balance.
#99
Correctly deference mint_mode and default to 'fixed' when not set
#94
bugfix: fix env and import base64
#97
Fix http session for dft mint entries
#96
Perpetual Toking Mining ARC20 with Bitwork
#93
add ENABLE_RATE_LIMIT for customization
#88
Use a fixed pylru with to avoid key deletion exceptions
#81
feature: support http protocol
#58
Atomicals ElectrumX Node v1.3.8.2
Atomicals ElectrumX Node v1.3.8.1
Atomicals ElectrumX Node v1.3.8.0
Deploy #ARC20 tokens that can be mined forever with exponentially increasing Bitwork mining targets.
Bitcoin Block Activation Height: 828,128
No re-sync required. It is strongly recommended to apply this upgrade as soon as possible. Must be used with CLI https://github.com/atomicals/atomicals-js >= Version 0.1.70
Changes:
Perpetual Toking Mining ARC20 with Bitwork
#93
add ENABLE_RATE_LIMIT for customization
#88
Use a fixed pylru with to avoid key deletion exceptions
#81
feature: support http protocol
#58
Atomicals ElectrumX Node v1.3.7.5
The purpose of this release is to optimized the processing of blocks with large number of decentralized FT mints (DFTs) in them. Prior to this release it would take O(n^2) time to process in the number of minted DFT items for a given ticker. Now the performance is O(n). To compare the performance it is about a 100x speed up in practice during heavy DFT mints.
Changes:
Optimize processing of DFTs, clean up logging levels, and add extra caching layers
#61
Atomicals ElectrumX Database Snapshots:
- Latest at block height 824012: https://cdn.atomicals.xyz/snapshots/824012/index.html
- Genesis at just before block height 808080: https://cdn.atomicals.xyz/snapshots/genesis/index.html
Atomicals ElectrumX Node v1.3.7.4
The purpose of this release is to relieve some pressure when processing a new block with many DFT mints in it. The b'gi' index is queried on every DFT mint which could be huge (ie: some tokens have max mints of 500,000) and it leads to quadratic number of lookups in essence. Therefore the main driver of this release is to use an intermediate cache that performs only 2 lookups to the DB per block. 1 to load the count persistent on disk and another to query at the end of the block to finalize to ensure no accidental inflation bug was added
Changes:
Add dft mint counter cache to speed up processing many dfts in same block
#56
support get_address_from_output_script
#55