491e79b8e6
Unified terminology from block "generator", "forger", etc. to "minter" Unified terminology "proxy forger" to "reward share" as it was incorrect, or at least highly ambiguous, which account had which role. AccountRepository.findRewardShares() has different arg order! Account.canMint() now returns true if account has 'founder' flag set. Added Account.canRewardShare() which returns whether acocunt can create a reward-share (e.g. level 5+ or founder). Fixed HSQLDBAssetRepository.getAllAssets() which had incorrect resultSet column indexes. Removed old traces of EnableForging transaction. ACCOUNT_LEVEL and ACCOUNT_FLAGS (genesis-block-only transaction types) now set target account's last-reference. This is allow later REWARD_SHARE transactions in genesis block and post-genesis transactions by that account. REWARD_SHARE transactions are now FREE, but only if minter is also recipient. If a self-reward-share already exists, then unless share-percent is zero (to terminate reward-share), any subsequent self-reward-share is invalid. Updated SysTray i18n properties file. BlockChain config file requires 'minAccountLevelToRewardShare' and optional 'minAccountLevelToMint'. Added potential, but currently unused, memory-hard PoW algorithm. Fixed/removed/disabled some unit tests. BlockMinter.generateTestingBlock asks Controller to pretend mintingAccount is 'online'. More testing needed!
((Qora2)) - Qortal Project - Official Repo
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.jarto 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.