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.

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

Question about usage of Waves Platform #120

Open
emeth- opened this issue Sep 13, 2018 · 2 comments
Open

Question about usage of Waves Platform #120

emeth- opened this issue Sep 13, 2018 · 2 comments

Comments

@emeth-
Copy link

emeth- commented Sep 13, 2018

Hey there,

As I was browsing through the code, I noticed this project appears to be forked from Waves Platform.

7ee9d5f
wavesplatform/Waves@7ee9d5f

What does this project use from Waves? And how is it different from Waves?

Thanks, I'm really interested in what you guys are attempting to solve here with VEE.

@ncying
Copy link
Contributor

ncying commented Sep 13, 2018

Hi Emeth, the short answer is yes, you are correct. We used some basic infrastructure from Scorex and Waves to speed up development, like nodes design, communication among nodes and leasing features. One doesn't have to re-invent the wheel.

Having said that, VEE's goal and vision are completely different. Our first release has implemented our new consensus mechanism called Supernode Proof of Stake, a.k.a. SPoS with future plans to build a general-purpose blockchain database in which data and information can be represented in a descriptive manner while preserving integrity. This allows for faster development and adoption of blockchain powered applications.

@emeth-
Copy link
Author

emeth- commented Sep 13, 2018

Definitely, makes complete sense.

So I see the SPoS consensus, which is great. The future plans to build the general-purpose blockchain database described in the whitepaper - what is the deal with that? Is the idea that you will do a token sale to obtain funds to pay your developers to build that piece?

I note no significant details on how such a feature will be built in the whitepaper or code-base, other than a description of how Namecoin did their piece. Are those details not worked out yet, and part of the money raised from the token sale will also go in paying people to come up with those details?

To be super clear, my question is about the plan for exactly how to achieve your Create/Update/Delete/Search database functionality on the blockchain. Do you guys currently have a plan, or is generating such a plan part of what the token sale will fund? And if you do have a plan, when will it be published?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants