Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Do you plan to merge the v1.8.x branch code? #132

Closed
cppfuns opened this issue Oct 30, 2019 · 5 comments
Closed

Do you plan to merge the v1.8.x branch code? #132

cppfuns opened this issue Oct 30, 2019 · 5 comments

Comments

@cppfuns
Copy link

cppfuns commented Oct 30, 2019

RT
@Thaipanda
Copy link

not all v1.8.x code, what is the most important is EOSVM, which is under merging

@cppfuns
Copy link
Author

cppfuns commented Nov 9, 2019

Why not upgrade to 1.8.x overall? And after the 2.x branch, there should be a lot of new features and stability advantages

@Thaipanda
Copy link

BOSCore has its own roadmap and plan, some features will pick from EOSIO, for example VM 2.0, Web Authn etc.

can you give some suggestion, which feature you want to have and why？

@matthewdarwin
Copy link

I would like database-map-mode = locked so I can run the entire blockchain in RAM and I don't need fast disks.

@cppfuns
Copy link
Author

cppfuns commented Mar 9, 2020

Recently, I tried to move the function of the original 1.6.3 version to 2.0, and found that many data structures have changed, and I couldn't find a corresponding method. It is indeed difficult to upgrade.

@cppfuns cppfuns closed this as completed Mar 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@cppfuns @matthewdarwin @Thaipanda