Pages:
Author

Topic: Scorex - Ultracompact Cryptocurrency Engine for Researchers - page 2. (Read 4941 times)

full member
Activity: 317
Merit: 103
never heard of this scam before must be new looking to get rich quick

Hello forum robot, I love you too  Grin
legendary
Activity: 826
Merit: 1002
amarha
never heard of this scam before must be new looking to get rich quick

LOL. Did you actually read the post to see what this is?
legendary
Activity: 1764
Merit: 1000
never heard of this scam before must be new looking to get rich quick
full member
Activity: 317
Merit: 103
The first article describing architecture of almost every cryptocurrency of today has been just published: https://github.com/ConsensusResearch/Scorex-Lagonaki/blob/master/docs/components.md
legendary
Activity: 2464
Merit: 1145
Very cool project subscribing!
full member
Activity: 317
Merit: 103
First Scorex devs meetup is coming! Aug, 14th, Saint-Petersburg, Russia. Going to publish some design docs before that.
full member
Activity: 317
Merit: 103
Made a lot of small improvements and some little fixes during last few days. Codebase is mostly ready for forking
full member
Activity: 317
Merit: 103
The only place we can view information on this is on GitHub?

Right, 2 files on GitHub(API/Readme) + source code. Will write some docs on architecture / details.

Very interesting. Sadly, I know nothing about Scala. Sad

Is part of the idea to make the code as short as possible? Kind of like those <1 kB chess programs that attempt to do the same? If so, wouldn't adopting proof-of-work rather than proof-of-stake help simplify things even further? Or are proof-of-stake systems not significantly more complex than proof-of-work systems?

With PoS it's simpler to run smaller networks, even a single running blockchain on a local machine. Both PoS algos implemented are pretty simple in fact  Smiley
sr. member
Activity: 406
Merit: 250
Very interesting. Sadly, I know nothing about Scala. Sad

Is part of the idea to make the code as short as possible? Kind of like those <1 kB chess programs that attempt to do the same? If so, wouldn't adopting proof-of-work rather than proof-of-stake help simplify things even further? Or are proof-of-stake systems not significantly more complex than proof-of-work systems?
member
Activity: 63
Merit: 10
I'm going to have a lot of fun with this tool.

Thanks kushti and arduiman Smiley
hero member
Activity: 597
Merit: 500
hero member
Activity: 756
Merit: 506
The only place we can view information on this is on GitHub?
hero member
Activity: 597
Merit: 500
very cool, congrats kushti.
full member
Activity: 317
Merit: 103
Motivation

There are two huge problems around cryptocurrencies development project Scorex aims to help to solve:

* Bitcoin source code contains more 100K lines of code(80K of C++ only), Nxt is about more than 45K lines of Java code. All parts of the design(network/transactions/consensus layers) are mixed in a hard way.  So researchers & developers are definitely not in a good start position to make any experiments.  In opposite, Scorex is less than _4K lines of Scala code_. Transactions layer is as simple as just tokens transfers. Consensus algo  could be switched easily(with two consensus algos out of the box,  one could be replaced with an another with just one line of code edited!)

* Major coins forks are trying to make IPO immediately, often having just one or two pretty controversial features introduced. **Scorex is intentionally not production-ready**, so please participate in any  non-commercial experiments built on top of it, but don't buy tokens unless you are 100+% sure what are you doing.
 

Features

* Two 100% Proof-of-Stake consensus algos out of the box, Nxt-like and Qora-like. One algo could be replaced
with an another with just one line of code edited (in Constants.scala)
* Simplest transactions model
* Asynchronous network layer on top of TCP(with Akka I/O)
* JSON API
* Command line client for the JSON API
* Curve25519 for signatures
* CC0(Public Domain) license
* Compact, functional, actors-powered code
* Scala / Akka
 

Roadmap

This release is named Lagonaki (after picturesque mountains resort in West Caucasus https://yandex.ru/images/search?text=%D0%BB%D0%B0%D0%B3%D0%BE%D0%BD%D0%B0%D0%BA%D0%B8 ), the current version is 1.0. It is the initial release aiming to provide modular and simple product to improve.
     
There are some issues/todos to be solved in upcoming 1.1 then 1.2 versions.           
 
And new branch will be forked very soon, with a brand new Proof-of-Stake algo having no whitepaper atm. More details soon. Nxt forging algo improvement proposal will be derived then from testing results. 

Authors

Scorex is made by [Consensus Research microteam](https://github.com/ConsensusResearch) previously worked on Proof-of-Stake investigation:

Alexander Chepurnoy aka kushti - Nxt developer & smartcontract.com cofounder. Has few published papers in Computer Science field(finite state systems related), writing PHD at the moment.   

andruiman - serial entrepreneur with theoretical physics background, a big fan of Coq interactive theorem prover & functional programming.   


Contributions

We're highly welcome contributions in form of pull requests, testing, issues reporting, and forking for sure Smiley


Donations

Also we would be happy to get donations. You can buy our asset on Nxt Assets Exchange: https://trade.secureae.com/#5841059555983208287, Bitcoin wallet is **17YksFD7eRB4NhPfEtGrGnuvuwpkAeBd7f** .   
   


Repository URL

The main link to follow is the GitHub repository:

https://github.com/ConsensusResearch/Scorex-Lagonaki

 
Pages:
Jump to: