Public Release
See original GitHub issue- Make sure all crypto methods are working as intended for v1
- Make sure all BigInt methods are working as intended for v1
- Make sure syncing is decently fast
- Make sure node gets discovered on network to be sent some blocks
- Remove console.log spam and proof read log messages (leave it for devnet for now)
- Proof read test descriptions and adjust if needed
- Fix delegate monitor in explorer
More will be added later
Important
- Decide package version before devnet launch -
0.1.0
will be the initialdevnet
release
This one is especially important as we need to publish packages before going public or someone else can clone the repository and publish the packages under @arkecosystem
.
As we are on devnet
we should start with version 0.1.0
on every package. After that we have 2 options.
- Start with
0.1.0
duringdevnet
and tag1.0.0
of each package formainnet
and2.0.0
of each package once the v2 hardfork happens. - Start with
0.1.0
and tag1.0.0
once the hardfork happens.
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Justice News | DOJ
'Tis the season for holiday scams. Learn more about common fraud schemes this time of year and tips to protect yourself at http://fbi.gov/holidayscams....
Read more >Press Releases - U.S. Department of Education
Today, the U.S. Department of Education's Office for Civil Rights (OCR) announced that the Davis Joint Unified School District in California has entered...
Read more >Public Release - SoundCloud
Play Public Release on SoundCloud and discover followers on SoundCloud | Stream tracks, albums, playlists on desktop and mobile.
Read more >Public Release - Darpa
Is your work considered fundamental research and exempt from public release review? Please see the DARPA Fundamental Research page. Tags. | Agency |...
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 FreeTop 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
Top GitHub Comments
I kind of like option 1 better than option 2, gives more structure.
Was this all sorted out?