Qortal Core - Main Code Repository Decentralized Data Network - Blockchain - TRUE Cross-Chain Trading - Application and Website Hosting - Much More - Qortal is the future internet infrastructure for the global digital world.

Go to file

catbref 7f4511cb7b Networking and repository Some pom.xml changes to reduce maven-shade-plugin conflicting classes warnings. Repository now supports SAVEPOINT and ROLLBACK TO SAVEPOINT. HSQLDB concurrency/transaction model changed from LOCKS to MVCC to help with transaction deadlocks/rollbacks. More XXXs and TODOs added to Block.java for investigation/fix/improvements. Also used new repository SAVEPOINT feature when validating transactions instead of rolling back entire transaction. This fixes problem during synchronization where the rollback would undo previously synchronized, but not yet committed, blocks! Transactions orphaned by Block.orphan ARE now added to unconfirmed pile, unlike before. Concurrent lock now prevents simultaneous block generation and synchronization, including synchronization via multiple peers. Lots of new networking code: peer lists, block signatures, blocks, blockchain synchronization. PEERS_V2 message now supports hostnames, IPv6 and port numbers. Fixed bug with block serialization for transport over network.		2019-02-01 14:03:06 +00:00
.settings	Unify API calls that return lists + offload pagination to repository	2019-01-24 16:42:55 +00:00
lib/org	Files missing from previous commit (somehow)	2018-12-03 13:12:52 +00:00
src	Networking and repository	2019-02-01 14:03:06 +00:00
.classpath	Interim networking code commit in case of dev catastrophe!	2019-01-30 18:24:10 +00:00
.gitignore	Transaction-specific info in API results	2018-12-13 08:44:50 +00:00
.project	initial work towards OSGi	2019-01-04 10:19:33 +00:00
blockchain.json	API, switchable MD160,	2019-01-07 13:12:42 +00:00
log4j2.properties	Networking and repository	2019-02-01 14:03:06 +00:00
osgi-console.sh	initial work towards OSGi	2019-01-04 10:19:33 +00:00
pom.xml	Networking and repository	2019-02-01 14:03:06 +00:00
README.md	Unit test fixes + initial CIYAM AT integration	2018-10-04 14:38:59 +01:00
settings.json	FATJAR packaging + block explorer changes	2018-12-05 11:32:55 +00:00

README.md

Qora2

To use:

Use maven to fetch dependencies.
Build project.
Build v1feeder.jar as a fatjar using src/v1feeder.java as the main class
Fire up an old-gen Qora node.
Use v1feeder.jar to migrate old Qora blocks to DB:

java -jar v1feeder.jar qora-v1-node-ip

You should now be able to run all the JUnit tests.

You can also examine the migrated database using HSQLDB's "sqltool".

It's a good idea to install "rlwrap" (ReadLine wrapper) too as sqltool doesn't support command history/editing!

Typical command line for sqltool would be:

rlwrap java -cp ${HSQLDB_JAR}:${SQLTOOL_JAR} org.hsqldb.cmdline.SqlTool --rcFile=${SQLTOOL_RC} qora

${HSQLDB_JAR} contains pathname to where Maven downloaded hsqldb, typically ${HOME}/.m2/repository/org/hsqldb/hsqldb/2.4.0/hsqldb-2.4.0.jar, but for now lib/org/hsqldb/hsqldb/r5836/hsqldb-r5836.jar

${SQLTOOL_JAR} contains pathname to where Maven downloaded sqltool, typically ${HOME}/.m2/repository/org/hsqldb/sqltool/2.4.1/sqltool-2.4.1.jar

${SQLTOOL_RC} contains pathname to a text file describing Qora2 database, e.g. ${HOME}/.sqltool.rc, with contents like:

urlid qora
url jdbc:hsqldb:file:db/qora
username SA
password

urlid qora-test
url jdbc:hsqldb:file:db/test
username SA
password

You could change the line url jdbc:hsqldb:file:db/test to use a full pathname for easier use.

Another idea is to assign a shell alias in your .bashrc like:

export HSQLDB_JAR=${HOME}/.m2/repository/org/hsqldb/hsqldb/2.4.0/hsqldb-2.4.0.jar
export SQLTOOL_JAR=${HOME}/.m2/repository/org/hsqldb/sqltool/2.4.1/sqltool-2.4.1.jar
alias sqltool='rlwrap java -cp ${HSQLDB_JAR}:${SQLTOOL_JAR} org.hsqldb.cmdline.SqlTool --rcFile=${SQLTOOL_RC}'

So you can simply type: sqltool qora-test

Don't forget to use SHUTDOWN; before exiting sqltool so that database files are closed cleanly.