Author

Topic: [old thread] - RISE | DPOS | APPS & DAPPS - page 582. (Read 653331 times)

hero member
Activity: 1204
Merit: 521
Can to participate Jr. Members in Signature Champagn?
What to write in a form for registration? It starts as Members…
legendary
Activity: 1526
Merit: 1003
Is there any spreadsheet to see the status of participants and what is deadline to join the social media campaign?
hero member
Activity: 728
Merit: 500
Cloak Creator and Veritise - www.vcode.tech - See
full member
Activity: 196
Merit: 100
RISE Team Account
hero member
Activity: 762
Merit: 500
whats different from xcr or lisk . thanks
It's like crypti 3.0, just kidding  Cheesy
hero member
Activity: 1484
Merit: 598
whats different from xcr or lisk . thanks

It is clone lisk
may be a little diffrerent. but i dont know what different from xcr or lisk.
full member
Activity: 135
Merit: 100
whats different from xcr or lisk . thanks
sr. member
Activity: 247
Merit: 250
look interesting ,changed my Signature
member
Activity: 106
Merit: 10
seems closer to release
legendary
Activity: 2226
Merit: 1014
Follow and RT your tweet on twitter.
please add me to the list.
https://twitter.com/Yns1971
dev me too i follow and RT
https://twitter.com/pacellidavide
add my name to for the bounty! thanks!
sr. member
Activity: 399
Merit: 250
Follow and RT your tweet on twitter.
please add me to the list.
https://twitter.com/Yns1971
legendary
Activity: 2226
Merit: 1014
full member
Activity: 180
Merit: 100
AO Blockchain Founder | Lead Developer
So how does RISE differ from LISK?

In code, at this point, not very much.

We picked LISK as a starting point due to how it was designed to run Smart Contract, Dapps, and had an easy to use, nearly ubiquitous programming language as it's base, to have the widest possible audience to start with.

We are going to change the codebase to move away from Relational database as a backend, and use an object / document oriented database instead. This will enable flexibility in building Dapps data stores, since this style of database is traditionally schema-less.

We are also going to build in LetsEncrypt, to ensure all Nodes have SSL encrypted and Enforced, Nodes will be built automatically either utilizing docker or a shell script. (This is similar to what LISK does)

Additionally, we are going to be running consistent security audits on the entire infrastructure, utilizing a holistic approach to penetration testing that I have used in the past. We will combine black-box penetration testing with authenticated vulnerability scanning. This of course will include social engineering attack vectors to ensure that our network, infrastructure, and codebase remain clean. Of course, the community can help with the code base, as it will be kept current on github.

Initially, we will be running all delegates, and we will always maintain a total of 101 nodes with 101 delegates. After the ICO, we will also form the "Rise Vision" foundation - more details on it's structure will be to follow, but ultimately it's goal will be to steer RISE into the future.

Our biggest difference is we are not going to be a Code Only Application development platform. We will enable GUI based Smart Contract / Dapp development through our Web, Desktop, and possibly mobile applications.

I am working on a white paper detailing this, along with our roadmap for feature development and other details about our security posture, GUI dev tools, ect.
full member
Activity: 196
Merit: 100
RISE Team Account
Hi! I just noticed the sig design doesn't look right on Google Chrome, Mac OS X & on Firefox, Mac OS X:


Thanks for pointing this out Instacash.

We've notified the person that designed the sigs.
hero member
Activity: 1806
Merit: 515
So how does RISE differ from LISK?
full member
Activity: 180
Merit: 100
AO Blockchain Founder | Lead Developer
Congrats and very nicely done. I can run a node. How many delegates are you guys going to need?

We are unsure how many delegates at this point in time. Minimum of 101.

However, we are looking at doing a variable amount based on the volume of transactions on the blockchain over a day to day basis. I'm not entirely sure what that will look like, but I don't think 101 is enough to provide a reasonably secure system at higher volumes. But doing much more than that isn't feasible at low values, as we will be to start out with.

More details to come on this later, but this is our current thinking.
hero member
Activity: 798
Merit: 500
Hi! I just noticed the sig design doesn't look right on Google Chrome, Mac OS X:



& on Firefox, Mac OS X:

full member
Activity: 224
Merit: 100
Good news , I hope Rise team and the community is always solid
My RISE investment just got cut in half in a matter of seconds  Cheesy Cheesy

 Tongue
sr. member
Activity: 729
Merit: 250
Good news , I hope Rise team and the community is always solid
full member
Activity: 224
Merit: 100
Got my sig. Looking good. Hopefully nobody else joins in so I can get my 300,000 RISE  Grin
Jump to: