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

This great work deserves more coverage. Waves is building on top of Scorex. Hopefully they'll use some funds to contribute back to core.

It is possible to connect to a public testnet right now, though public announce will be later, and Debian package / Docker image will be available soon. To connect to a public testnet, run current master on your machine: https://github.com/ScorexProject/Scorex .

Testnet will be alive for few weeks and later will be updated with a new consensus algorithm with working name RollerChain 

Well, public testnet release will be on this week hopefully. And Wiki will be released during this week as well.

Scorex now is a part IOHK Research ( http://iohk.io/about/ ). It is (and will be) under CC0 license, and everyone is welcomed to contribute!

Cryptographic primitives have been externalized into separate framework scrypto: https://github.com/ScorexProject/scrypto

1.2.0-RC1 is out: TCP framing, peers handshaking, UPnP ports mapping, new p2p settings, a ton of bugfixes.

I'm going to start a wiki.

1. We're going to launch a testnet with Permacoin implementation as consensus module in coming days. PRE-ANN is there: https://bitcointalksearch.org/topic/pre-announce-permacoin-implementation-on-top-of-scorex-open-testing-1327860

2. Developers maillist: https://groups.io/g/scorex-dev

A lot of code just has been merged into master. P2P code redone(it's modular now as well as other parts of the core and allows custom plugins), and blocktree support has been added as well(so a node could store few blocks of a same height).

The only thing remains before 1.2.0 release is Permacoin dataset segments exchange via P2P network.

Thanks guys! Yes, we won the Hackathon with Permacoin prototype implementation, now we've implemented Permacoin as Scorex module, the only thing to run a testnet is data segments p2p protocol. I'm going to implement it, and then we're more or less ready to launch a testnet.

So we are looking for contributors! Please contribute with a hardware to run a fullnode with or without mining! 5-10 nodes are okay for start

And we're starting to welcome developers to look into the code!

Cool stuff, congratulations!

Scorex team won on Moscow blockchain hackathon http://forklog.net/moscow-blockchain-hackathon-winning-team-proves-the-permacoin-algorithm/ and working on permacoin consensus algo

At the moment Scorex uses this implementation: https://github.com/vRallev/ECC-25519 . I have a plan to switch to implementation from WhisperSystems if my trivial pull-request about possibility of keypair generation with a given seed will be merged (https://github.com/WhisperSystems/curve25519-java/pull/7).

It would be good to get both Curve25519 reviewed. Also it would be good to get some more signature schemes under the hood.

And another direction about crypto primitives, the cryptographic hash function. While Scorex is using SHA-256 from JDK, it would be good to get Blake2 implementation under the hood (https://blake2.net/). It would be also good to compare its performance with SHA-2/3 in the JVM.
 

I may want to collaborate with you guys at some point. I've been coding in Scala as well. I began to port EdDSA from Java I2P. When I get some time, I will look at your Curve25519 implementation.

Version 1.1.2 has been released with consensus-related API calls added. 1.2.0 roadmap has been considered, we're working towards it. Hopefully 1.2.0 will be done before the weekend

Awesome work. Congrats on getting sponsorship too.

1, Scorex Lagonaki 1.1.1 has been released! https://github.com/ScorexProject/Scorex-Lagonaki

2. Project got sponsorship from IOHK(new project of Charles Hoskinson)

3. A lot of refactoring is planned for next few days. Hopefully before Nov, 14th 1.2.0 milestone will be reached, and then a new submodule will be started.

Version 1.1.0 is released(more than week ago actually). 1.1.1 will be released in next few days.

It seems the project is getting to attract some donations, so hopefully the project is going to be developed at a faster pace.

I'm going to release 1.1.0 during this week, snapshot version is online. Just finished new article about new modular design, could be fun for devs: "On the Way to a Modular Cryptocurrency, Part 1: Generic Block Structure" -> https://github.com/ConsensusResearch/Scorex-Lagonaki/blob/master/docs/modular1.md

Version 1.0.4 with small improvements is just released. Next version will be 1.1.0 with (raw,but) modular design. The code for it is mostly ready, and divided now into 4 parts:

1. Scorex-Basics - crypto/utility functions, and interfaces for transaction/consensus modules

2. SimplestTransactions - implementation of a transaction module interface. simplest payment transactions, no transactions/state merkle roots in block etc. Probably having some flaws

3. LagonakiConsensus - implementation of a consensus module interface. Two Proof-of-Stake implementations, Nxt-Like & Qoralike

4. Scorex Lagonaki, the runnable application = Basics+SimplestTransactions+LagonakiConsensus+business-logic & APIs on top of that.


Design will be improved further, resulting in some 1.2.x release ready for forking. Also started to write explanatory / education comments for the code.


The project got some sponsorship, so we can buy some development efforts(and publish results under public domain, thanks sponsor!). As resources are pretty limited anyway, forking will be done as follows:

1. Few forking proposals will be described in form of Scorex Forking Proposal(SFP). E.g. Ethereum VM support(using EthereumJ code), pos experiments, Permacoin, Bill White's lightweight ledgers proposal w. more scalable transaction layer etc.

2. Voting amongst ConsensusResearch shareholders(we made some fundrasing via Nxt AssetsExchange: https://nxtforum.org/consensus-research/first- fundraising-letter/) over Nxt Blockchain. Please note voting results will be taken into an account, but implementation of a winner is not guaranteed.

3. Implementation of some proposal

The meetup was very productive and insightful, finally we've came to conclusion to split the project into separate layers explicitly using following artefacts:

1. scorex-utils - cryptofunctions and other functionality not corresponding to a cryptocurrency logic directly
2. scorex-network - p2p layer
3. scorex-consensus - consensus-related data sctructure & functions
4. scorex-transaction - transactions handling code and internal state


So to change consensus from PoS to PoW it would be enough to swap from scorex-consensus-pos to scorex-consensus-pow.

I'm going off for few days to return with a roadmap.

Yes, it's not hard to change to PoW I guess

Great project.  Very educational.

Is it compatible with proof-of-work?