Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[2.6][T4] Discussion: Set 'Version: 2' as default or make it easier to configure

See original GitHub issue

When creating a transaction with the TransactionBuilder and signing it with the ‘regular’ .sign() function, set Version to 2 by default. Alternatively, make it easier to mutate the value, other than modifying the configManagers.


  1. Version: 2 transactions will be the new standard as Version: 1 are is going to be deprecated in the future. Therefore, the SDK user should not have to put in extra effort to create a transaction that is now the default.

  2. Simplicity. The SDK should be easy to use and having to set Managers.configManager.setHeight(4006000); (devnet) does not fit this picture.

Have the .builder() function support Version: 2 transactions. With the TransactionBuilder it is currently already possible to set the Version with the .version() function, however an error is returned while trying to build the transaction with the .build() function; UnhandledPromiseRejectionWarning: TransactionVersionError: Version 2 not supported.

Your Environment @arkecosystem/crypto: 2.6.0-next.2

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:1
  • Comments:13 (4 by maintainers)

github_iconTop GitHub Comments

faustbriancommented, Oct 23, 2019

We could default the package to require v2 transactions but this would be a breaking change which could affect all forks and bridgechains and things like wallets so this needs to be done with a long enough heads up for those to adjust.

The desktop wallet for example would need to switch between v1 and v2 transactions depending on the network as some networks might lag behind with applying the 2.6 update.

I’ll bring this up internally as it makes sense for ARK itself to default to 2.0 and think about how to best approach this without breaking potentially affected applications and bridgechains.

ghostcommented, Jun 30, 2020

This issue has been closed. If you wish to re-open it please provide additional information.

Read more comments on GitHub >

github_iconTop Results From Across the Web

The sealed-bid abstraction in online auctions - Document
This paper presents five empirical tests of the popular modeling abstraction that assumes bids from online auctions with proxy bidding can be analyzed...
Read more >
Vyacheslav M. Labunskyy Editor - Ribosome Pro ling
For over 35 years, biological scientists have come to rely on the research protocols and methodologies in the critically acclaimed Methods in Molecular ......
Read more >
There is still much to be learned regarding the nature of the interaction between lexical tone and utterance-level intonation.
Read more >
contributors to and mitigators of black band disease in corals
community that targets BBD-associated cyanobacteria, (2) the establishment of methodologies to cultivate the main BBD cyanobacterium, R. reptotaenium, ...
Read more >
Get more instagram followers now, Drift mania 2 download, Burger disorder free? ... Wincom untethered jailbreak 6.1.3, Easy set pool 457 x 122, ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found