`Array size too big` after receiving block containing Ordinal NFT
See original GitHub issueThis block made Wasabi filter creation process to halt because NBitcoin said that Array size too big however next time it run it past. I cannot make it fail locally so, it seems there is some special condition that is not deterministic.
2023-02-01 20:38:39.917 [537] ERROR PeriodicRunner.ExecuteAsync (107) System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values. (Parameter 'Array size too big')
at NBitcoin.Protocol.VarString.StaticRead(BitcoinStream bs, Byte[]& bytes)
at NBitcoin.WitScript.ReadCore(BitcoinStream stream)
at NBitcoin.Witness.ReadWrite(BitcoinStream stream)
at NBitcoin.Transaction.ReadWrite(BitcoinStream stream)
at NBitcoin.BitcoinStream.ReadWrite[T](T& data)
at NBitcoin.BitcoinStream.ReadWrite[T](List`1& list)
at NBitcoin.Block.ReadWrite(BitcoinStream stream)
at NBitcoin.Block.Parse(String hex, ConsensusFactory consensusFactory)
at NBitcoin.RPC.RPCClient.GetBlockAsync(uint256 blockId, CancellationToken cancellationToken)
at WalletWasabi.BitcoinCore.Rpc.RpcClientBase.GetBlockAsync(uint256 blockHash, CancellationToken cancellationToken)
at WalletWasabi.Extensions.TaskExtensions.WithAwaitCancellationAsync[T](Task`1 task, CancellationToken cancellationToken)
at WalletWasabi.Cache.IdempotencyRequestCache.GetCachedResponseAsync[TRequest,TResponse](TRequest request, ProcessRequestDelegateAsync`2 action, MemoryCacheEntryOptions options, CancellationToken cancellationToken)
at WalletWasabi.Cache.IdempotencyRequestCache.GetCachedResponseAsync[TRequest,TResponse](TRequest request, ProcessRequestDelegateAsync`2 action, MemoryCacheEntryOptions options, CancellationToken cancellationToken)
at WalletWasabi.BitcoinCore.Rpc.CachedRpcClient.GetBlockAsync(uint256 blockHash, CancellationToken cancellationToken)
at WalletWasabi.Blockchain.Blocks.BlockNotifier.ActionAsync(CancellationToken cancel)
at WalletWasabi.Bases.PeriodicRunner.ExecuteAsync(CancellationToken stoppingToken)
NBitcoin version: v7.0.14
This is the block: 0000000000000000000515e202c8ae73c8155fc472422d7593af87aa74f2cf3d
Issue Analytics
- State:
- Created 8 months ago
- Reactions:2
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Scalable Generative Inscriptions on BTC · ordinals ord
Generative NFTs can create a rich set of NFTs at very small data sizes. ... of inscribing large collections we may devise an...
Read more >What are Bitcoin Ordinals? All About Bitcoin NFTs
Bitcoin NFTs surge amidst collectibles bear market, but what makes Ordinals different?
Read more >NFTs Are Bloating Bitcoin, Creating Risks And ...
SegWit increased Bitcoin's block size from 1 megabyte to 4 megabytes and Taproot loosened requirements for data limits, allowing the full 4 ...
Read more >Unveiling the Mysteries of Ordinal Inscriptions
Because the block size has an upper limit (about 1 MB), miners will give priority to confirm transactions with high transaction rate ...
Read more >Bitcoin Ordinals – Will The Bitcoin NFT Ecosystem be ...
Segwit and Taproot upgrades have changed the block size of Bitcoin which has made a path for Ordinals. Recently, a report by Galaxy...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

7.0.14 Failure
7.0.16 Succeed
Still don’t understand how it is that we are not affected.
Umm that was added in version 7.0.16 and we have 7.0.14, however we are not stuck. I will do some better tests and go back with results.