crowetic/qortal
1
0
Fork 0
forked from Qortal/qortal
Code Pull Requests Activity
qortal/src/main/resources/blockchain.json

498 lines
46 KiB
JSON
Raw Normal View History

Blockchain config (ncluding genesis block) moved out into config file
2018-12-17 13:28:37 +00:00
{
NTP and performance changes + fixes. New NTP class now runs as a simplistic NTP client, repeatedly polling several NTP servers and maintaining a more accurate time independent of operating system. Several occurrences of System.currentTimeMillis() replaced with NTP.getTime() particularly where block/transaction/networking is involved. GET /admin/info now includes "currentTimestamp" as reported from NTP. Added support for block timestamps determined by generator, instead of supplied by clock. (BlockChain.newBlockTimestampHeight - not yet activated). Incorrect timestamps will produce a TIMESTAMP_INCORRECT Block.ValidationResult. Block.calcMinimumTimestamp repurposed as Block.calcTimestamp for above. Block timestamps are now allowed to be max 2000ms in the future, was previously max 500ms. Block generation prohibited until initial NTP sync. Instead of deleting INVALID unconfirmed transactions in BlockGenerator, Controller now deletes EXPIRED unconfirmed transactions every so often. This also fixes persistent expired unconfirmed transactions on nodes that do not generate blocks, as BlockGenerator.deleteInvalidTransactions() was never reached. Abbreviated block sigs added to log entries declaring a new block is generated in BlockGenerator. Controller checks for NTP sync much faster during start-up and SysTray's tooltip text starts as "Synchronizing clock" until NTP sync occurs. After NTP sync, Controller logs NTP offset every so often (currently every 5 mins). When considering synchronizing, Controller skips peers that have the same block sig as last time when synchronization resulted in no action, e.g. INFERIOR_CHAIN, NOTHING_TO_DO and also OK. OK is included as another sync attempt would result in NOTHING_TO_DO. Previously this skipping check only happened after prior INFERIOR_CHAIN. During inbound peer handshaking, if we receive a peer ID that matches an existing inbound peer then send peer ID of all zeros, then close connection. Remote end should detect this and cleanly close connection instead of waiting for handshake timeout. Randomly generated peer IDs have lowest bit set to avoid all zeros. Might need further work. Networking doesn't connect, or accept, until NTP has synced. Transaction validation can fail with CLOCK_NOT_SYNCED if NTP not synced.
2019-07-31 16:08:22 +01:00
"blockTimestampMargin": 2000,
New synchronizer and other improvements API call GET /addresses/online reports online accounts, including both addresses relating to the proxy-forge public key. New PeerChainTipData class to replace the broken "peer data lock" that was supposed to make sure peer's last height/blockSig/timestamp were all in sync. Now peer's chain tip data is a single object reference that can be replaced in one go. Removed pointless API calls /blocks/time and /blocks/{generatingbalance}. Various changes, mostly in Block class, to do with switching to BlockTimingByHeight from old min/max block time. New block 'weight' based on number of online accounts and 'distance' of perturbed generator public key from 'ideal' public key (for that particular block's height). New sub-chain 'weight' based on accumulating block weights, currently by shifting previous accumulator left by 8 bits then adding next block's weight. More validation of BlockChain config. Helpful for debugging, probably not very useful to end-users. BlockGenerator now uses unified Peer predicates from Controller, like: Controller.hasMisbehaved, Controller.hasNoRecentBlock, etc. Controller now keeps a list of chain-tip signatures that are for inferior chains, so it doesn't try to synchronize with peers with inferior chains. (This list is wiped when node's blockchain changes/block is generated). Controller now asks Gui to display error box if it can't parse Settings. Controller.potentiallySynchronize() does more filtering of potential peers before calling actuallySynchronize(). (Mostly moved from Synchronizer, so now we expect actuallySynchronize() to do something rather than bail out because it doesn't like the peer after all). If synchronization discovers that peer has an inferior chain, then Controller notifies that peer of our superior chain, to help keep the network in sync. Renamed OnlineAccount to OnlineAccountData, as it is in package org.qora.data after all... Synchronizer reworked to request block summaries so it can judge which chain is better, and hence whether to sync with peer or abort. Slight optimization of Peer.readChannel() to exit earlier if no more network messages can be extracted from buffer. More tests. Improved documentation and logging.
2019-09-26 17:43:50 +01:00
"transactionExpiryPeriod": 86400000,
Add account level change due to blocks generated. Removed ENABLE_FORGING and related. Still to do: 'orphan' version of Block.increaseAccountLevels
2019-10-10 13:52:00 +01:00
"maxBlockSize": 2097152,
Blockchain config (ncluding genesis block) moved out into config file
2018-12-17 13:28:37 +00:00
"maxBytesPerUnitFee": 1024,
Add account level change due to blocks generated. Removed ENABLE_FORGING and related. Still to do: 'orphan' version of Block.increaseAccountLevels
2019-10-10 13:52:00 +01:00
"unitFee": "0.001",
Interim commit: online accounts and account levels Safety commit in case of data loss! Lots of changes to do with "online accounts", including: * networking + GET_ONLINE_ACCOUNTS * ONLINE_ACCOUNTS messages & handling + Changes to serialization of block data to include online accounts info * block-related + Adding online accounts info when generating blocks + Validating online accounts info in block data + Repository changes to store online accounts info * Controller + Managing in-memory cache of online accounts + Updating/broadcasting our online accounts * BlockChain config Added "account levels", so new code/changes required in the usual places, like: * transaction data object * repository * transaction transformer * transaction processing
2019-09-13 14:21:04 +01:00
"useBrokenMD160ForAddresses": false,
Performance fix & other minor fixes Fixed bug in GenesisBlock which wasn't stripping out ISSUE_ASSET transactions for v1 blockchains. Updated blockchain.json for v1 qora blockchain to fall into line with new BlockChain config unmarshalling code. Improved TransactionData.equals when comparing exact same object. Improved HSQLDBBlockRepository.getHeightFromTimestamp to use OffsetDateTime object, which includes time zone info, to fix incorrect SQL full-scan so that DB now does index-scan instead. Also converted use of MAX(column) to ORDER BY column DESC as MAX() not optimized when MVCC in effect. Added corresponding INDEX to Blocks on columns (generation, height); Similar MAX(column) to ORDER BY column DESC improvement for getBlockchainHeight(). Bumped size of HSQLDB TYPE ATTags from VARCHAR(32) to VARCHAR(80) Improved reflection-based method calls to rethrow underlying exceptions like DataException, TransformationException, etc. instead of losing them in general InvocationTargetException. Re-added atTransaction.toBytes() method so v1 transactions can be verified. Fixed extraneous additional copy of voter's public key when serializing in VoteOnPollTransactionTransformer.toBytes() Fix-up of v1feeder
2019-03-04 11:41:30 +00:00
"requireGroupForApproval": false,
"defaultGroupId": 0,
Interim commit: online accounts and account levels Safety commit in case of data loss! Lots of changes to do with "online accounts", including: * networking + GET_ONLINE_ACCOUNTS * ONLINE_ACCOUNTS messages & handling + Changes to serialization of block data to include online accounts info * block-related + Adding online accounts info when generating blocks + Validating online accounts info in block data + Repository changes to store online accounts info * Controller + Managing in-memory cache of online accounts + Updating/broadcasting our online accounts * BlockChain config Added "account levels", so new code/changes required in the usual places, like: * transaction data object * repository * transaction transformer * transaction processing
2019-09-13 14:21:04 +01:00
"oneNamePerAccount": true,
ProxyForging->RewardShare massive refactor & more... 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!
2019-10-29 17:46:55 +00:00
"minAccountLevelToRewardShare": 5,
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
"maxRewardSharesPerMintingAccount": 6,
Higher account levels more likely to win blocks Also: RewardShareKeys app now supports only one arg (minter private key) in self-reward-share mode, where recipient public key is derived from minter private key. Added methods to Account for returning 'effective' minting level where minting level for founders is read from blockchain config. (Or returns zero if unable to mint). Changed two Block constructors into static methods that return a new Block as there was way too much work being done to really be called a constructor, especially with all the opportunities to throw an exception too. Main blockchain config updated to reflect near-launch version. Added/changed blockchain weight tests to check block winning based on higher account levels.
2019-11-06 09:47:10 +00:00
"founderEffectiveMintingLevel": 10,
Interim commit: online accounts and account levels Safety commit in case of data loss! Lots of changes to do with "online accounts", including: * networking + GET_ONLINE_ACCOUNTS * ONLINE_ACCOUNTS messages & handling + Changes to serialization of block data to include online accounts info * block-related + Adding online accounts info when generating blocks + Validating online accounts info in block data + Repository changes to store online accounts info * Controller + Managing in-memory cache of online accounts + Updating/broadcasting our online accounts * BlockChain config Added "account levels", so new code/changes required in the usual places, like: * transaction data object * repository * transaction transformer * transaction processing
2019-09-13 14:21:04 +01:00
"onlineAccountSignaturesMinLifetime": 2592000000,
"onlineAccountSignaturesMaxLifetime": 3196800000,
Add extra entries to blockchain.json, remove HttpsTest, add Vanity Gen + minor whitespace / comment / JAXB mods Was commit e14381d: working on genesis block
2019-05-14 11:21:40 +01:00
"rewardsByHeight": [
Update blockchain.json to nearer launch version
2019-11-12 15:04:41 +00:00
{ "height": 1, "reward": 5.00 },
{ "height": 259201, "reward": 4.75 },
{ "height": 518401, "reward": 4.50 },
{ "height": 777601, "reward": 4.25 },
{ "height": 1036801, "reward": 4.00 },
{ "height": 1296001, "reward": 3.75 },
{ "height": 1555201, "reward": 3.50 },
{ "height": 1814401, "reward": 3.25 },
{ "height": 2073601, "reward": 3.00 },
{ "height": 2332801, "reward": 2.75 },
{ "height": 2592001, "reward": 2.50 },
{ "height": 2851201, "reward": 2.25 },
{ "height": 3110401, "reward": 2.00 }
Add extra entries to blockchain.json, remove HttpsTest, add Vanity Gen + minor whitespace / comment / JAXB mods Was commit e14381d: working on genesis block
2019-05-14 11:21:40 +01:00
],
Add account level change due to blocks generated. Removed ENABLE_FORGING and related. Still to do: 'orphan' version of Block.increaseAccountLevels
2019-10-10 13:52:00 +01:00
"sharesByLevel": [
{ "levels": [ 1, 2 ], "share": 0.05 },
{ "levels": [ 3, 4 ], "share": 0.10 },
{ "levels": [ 5, 6 ], "share": 0.15 },
{ "levels": [ 7, 8 ], "share": 0.20 },
{ "levels": [ 9, 10 ], "share": 0.25 }
Add extra entries to blockchain.json, remove HttpsTest, add Vanity Gen + minor whitespace / comment / JAXB mods Was commit e14381d: working on genesis block
2019-05-14 11:21:40 +01:00
],
Add account level change due to blocks generated. Removed ENABLE_FORGING and related. Still to do: 'orphan' version of Block.increaseAccountLevels
2019-10-10 13:52:00 +01:00
"qoraHoldersShare": 0.20,
Higher account levels more likely to win blocks Also: RewardShareKeys app now supports only one arg (minter private key) in self-reward-share mode, where recipient public key is derived from minter private key. Added methods to Account for returning 'effective' minting level where minting level for founders is read from blockchain config. (Or returns zero if unable to mint). Changed two Block constructors into static methods that return a new Block as there was way too much work being done to really be called a constructor, especially with all the opportunities to throw an exception too. Main blockchain config updated to reflect near-launch version. Added/changed blockchain weight tests to check block winning based on higher account levels.
2019-11-06 09:47:10 +00:00
"qoraPerQortReward": 250,
Add account level change due to blocks generated. Removed ENABLE_FORGING and related. Still to do: 'orphan' version of Block.increaseAccountLevels
2019-10-10 13:52:00 +01:00
"blocksNeededByLevel": [ 7200, 64800, 129600, 172800, 244000, 345600, 518400, 691200, 864000, 1036800 ],
More work on online accounts / blocks Block data now includes number of online accounts, as encoded online account indexes can't be validated by ConciseSet it seems. Corresponding changes to repository, transformer, block validation, data object, block summaries... Block timestamps are now calculated using parent block data and generator's public key, instead of old qora1 generating balance code. Generators are valid to forge if they have forging flag enabled. This will probably change to an account-level check in the near future. Added trimming of old online accounts signatures from blocks. Tidied up SysTray/BlockGenerator generation enabled/possible flag. Although we perform online accounts tasks (currently) every 10 seconds, only broadcast our online accounts every 60 seconds. In Controller.main(), if args are present then use first as a filename to settings JSON file (overriding the default filename). Still to do: change Block/BlockChain/Synchronizer to prefer blocks with more online accounts, failing that use generator nearest 'ideal', etc.
2019-09-18 14:49:47 +01:00
"blockTimingsByHeight": [
{ "height": 1, "target": 60000, "deviation": 30000, "power": 0.2 }
],
Blockchain config (ncluding genesis block) moved out into config file
2018-12-17 13:28:37 +00:00
"featureTriggers": {
Interim commit: online accounts and account levels Safety commit in case of data loss! Lots of changes to do with "online accounts", including: * networking + GET_ONLINE_ACCOUNTS * ONLINE_ACCOUNTS messages & handling + Changes to serialization of block data to include online accounts info * block-related + Adding online accounts info when generating blocks + Validating online accounts info in block data + Repository changes to store online accounts info * Controller + Managing in-memory cache of online accounts + Updating/broadcasting our online accounts * BlockChain config Added "account levels", so new code/changes required in the usual places, like: * transaction data object * repository * transaction transformer * transaction processing
2019-09-13 14:21:04 +01:00
"messageHeight": 0,
"atHeight": 0,
"newBlockDistanceHeight": 0,
"newBlockTimingHeight": 0,
"newBlockTimestampHeight": 0,
Performance fix & other minor fixes Fixed bug in GenesisBlock which wasn't stripping out ISSUE_ASSET transactions for v1 blockchains. Updated blockchain.json for v1 qora blockchain to fall into line with new BlockChain config unmarshalling code. Improved TransactionData.equals when comparing exact same object. Improved HSQLDBBlockRepository.getHeightFromTimestamp to use OffsetDateTime object, which includes time zone info, to fix incorrect SQL full-scan so that DB now does index-scan instead. Also converted use of MAX(column) to ORDER BY column DESC as MAX() not optimized when MVCC in effect. Added corresponding INDEX to Blocks on columns (generation, height); Similar MAX(column) to ORDER BY column DESC improvement for getBlockchainHeight(). Bumped size of HSQLDB TYPE ATTags from VARCHAR(32) to VARCHAR(80) Improved reflection-based method calls to rethrow underlying exceptions like DataException, TransformationException, etc. instead of losing them in general InvocationTargetException. Re-added atTransaction.toBytes() method so v1 transactions can be verified. Fixed extraneous additional copy of voter's public key when serializing in VoteOnPollTransactionTransformer.toBytes() Fix-up of v1feeder
2019-03-04 11:41:30 +00:00
"assetsTimestamp": 0,
Interim commit: online accounts and account levels Safety commit in case of data loss! Lots of changes to do with "online accounts", including: * networking + GET_ONLINE_ACCOUNTS * ONLINE_ACCOUNTS messages & handling + Changes to serialization of block data to include online accounts info * block-related + Adding online accounts info when generating blocks + Validating online accounts info in block data + Repository changes to store online accounts info * Controller + Managing in-memory cache of online accounts + Updating/broadcasting our online accounts * BlockChain config Added "account levels", so new code/changes required in the usual places, like: * transaction data object * repository * transaction transformer * transaction processing
2019-09-13 14:21:04 +01:00
"votingTimestamp": 0,
"arbitraryTimestamp": 0,
"powfixTimestamp": 0,
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
"qortalTimestamp": 0,
Interim commit: online accounts and account levels Safety commit in case of data loss! Lots of changes to do with "online accounts", including: * networking + GET_ONLINE_ACCOUNTS * ONLINE_ACCOUNTS messages & handling + Changes to serialization of block data to include online accounts info * block-related + Adding online accounts info when generating blocks + Validating online accounts info in block data + Repository changes to store online accounts info * Controller + Managing in-memory cache of online accounts + Updating/broadcasting our online accounts * BlockChain config Added "account levels", so new code/changes required in the usual places, like: * transaction data object * repository * transaction transformer * transaction processing
2019-09-13 14:21:04 +01:00
"newAssetPricingTimestamp": 0,
"groupApprovalTimestamp": 0
ProxyForging->RewardShare massive refactor & more... 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!
2019-10-29 17:46:55 +00:00
},
"genesisInfo": {
"version": 4,
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
"timestamp": "1583250000000",
ProxyForging->RewardShare massive refactor & more... 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!
2019-10-29 17:46:55 +00:00
"transactions": [
{ "type": "ISSUE_ASSET", "owner": "QUwGVHPPxJNJ2dq95abQNe79EyBN2K26zM", "assetName": "QORT", "description": "QORTAL coin", "quantity": 0, "isDivisible": true, "reference": "28u54WRcMfGujtQMZ9dNKFXVqucY7XfPihXAqPFsnx853NPUwfDJy1sMH5boCkahFgjUNYqc5fkduxdBhQTKgUsC", "data": "{}" },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ISSUE_ASSET", "owner": "QUwGVHPPxJNJ2dq95abQNe79EyBN2K26zM", "assetName": "Legacy-QORA", "description": "Representative legacy QORA", "quantity": 0, "isDivisible": true, "data": "{}", "isUnspendable": true },
Higher account levels more likely to win blocks Also: RewardShareKeys app now supports only one arg (minter private key) in self-reward-share mode, where recipient public key is derived from minter private key. Added methods to Account for returning 'effective' minting level where minting level for founders is read from blockchain config. (Or returns zero if unable to mint). Changed two Block constructors into static methods that return a new Block as there was way too much work being done to really be called a constructor, especially with all the opportunities to throw an exception too. Main blockchain config updated to reflect near-launch version. Added/changed blockchain weight tests to check block winning based on higher account levels.
2019-11-06 09:47:10 +00:00
{ "type": "ISSUE_ASSET", "owner": "QUwGVHPPxJNJ2dq95abQNe79EyBN2K26zM", "assetName": "QORT-from-QORA", "description": "QORT gained from holding legacy QORA", "quantity": 0, "isDivisible": true, "data": "{}", "isUnspendable": true },
ProxyForging->RewardShare massive refactor & more... 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!
2019-10-29 17:46:55 +00:00
Updated pre-launch blockchain config + fixes Fixed build timestamp parsing in Controller post reproducible build. Fixed REGISTER_NAME support in genesis block.
2020-01-24 11:35:30 +00:00
{ "type": "ACCOUNT_FLAGS", "target": "QY82MasqEH6ChwXaETH4piMtE8Pk4NBWD3", "andMask": -1, "orMask": 1, "xorMask": 0 },
{ "type": "ACCOUNT_FLAGS", "target": "QcPro2T97Q8cAfcVM4Pn4fv71Za4T6oeFD", "andMask": -1, "orMask": 1, "xorMask": 0 },
ProxyForging->RewardShare massive refactor & more... 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!
2019-10-29 17:46:55 +00:00
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_FLAGS", "target": "QbJqEntoBFps7XECQkTDFzXNCdz9R2qmkB", "andMask": -1, "orMask": 1, "xorMask": 0 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "ACCOUNT_FLAGS", "target": "Qc5sZS1Vb1ujj8qvL5uXV5y5yQPq6pw2GC", "andMask": -1, "orMask": 1, "xorMask": 0 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_FLAGS", "target": "QceNmCiZxxLdvL85huifVcnk64udcJ47Jr", "andMask": -1, "orMask": 1, "xorMask": 0 },
{ "type": "ACCOUNT_FLAGS", "target": "Qd453ewoyESrEgUab6dTFe2pufWkD94Tsm", "andMask": -1, "orMask": 1, "xorMask": 0 },
{ "type": "ACCOUNT_FLAGS", "target": "QfjoMGib4trpZHzxUSMdmtiRnsrLNf74zp", "andMask": -1, "orMask": 1, "xorMask": 0 },
{ "type": "ACCOUNT_FLAGS", "target": "Qgfh143pRJyxpS92JoazjXNMH1uZueQBZ2", "andMask": -1, "orMask": 1, "xorMask": 0 },
{ "type": "ACCOUNT_FLAGS", "target": "QicRwDhfk8M2CGNvpMEmYzQEjESvF7WrFY", "andMask": -1, "orMask": 1, "xorMask": 0 },
{ "type": "ACCOUNT_FLAGS", "target": "QLwMaXmDDUvh7aN5MdpY28rqTKE8U1Cepc", "andMask": -1, "orMask": 1, "xorMask": 0 },
{ "type": "ACCOUNT_FLAGS", "target": "QP3J3GHgjqP69neTAprpYe4co33eKQiQpS", "andMask": -1, "orMask": 1, "xorMask": 0 },
{ "type": "ACCOUNT_FLAGS", "target": "QPsjHoKhugEADrtSQP5xjFgsaQPn9WmE3Y", "andMask": -1, "orMask": 1, "xorMask": 0 },
{ "type": "ACCOUNT_FLAGS", "target": "QRt11DVBnLaSDxr2KHvx92LdPrjhbhJtkj", "andMask": -1, "orMask": 1, "xorMask": 0 },
{ "type": "ACCOUNT_FLAGS", "target": "QSbHwxaBh5P7wXDurk2KCb8d1sCVN4JpMf", "andMask": -1, "orMask": 1, "xorMask": 0 },
{ "type": "ACCOUNT_FLAGS", "target": "QTE6b4xF8ecQTdphXn2BrptPVgRWCkzMQC", "andMask": -1, "orMask": 1, "xorMask": 0 },
{ "type": "ACCOUNT_FLAGS", "target": "QUxh6PNsKhwJ12qGaM3AC1xZjwxy4hk1RG", "andMask": -1, "orMask": 1, "xorMask": 0 },
{ "type": "ACCOUNT_FLAGS", "target": "QXZk64nkBfGeaU8jFmaHtcDTG8ydwqZcWf", "andMask": -1, "orMask": 1, "xorMask": 0 },
{ "type": "ACCOUNT_FLAGS", "target": "QTx98gU8ErigXkViWkvRH5JfaMpk8b3bHe", "andMask": -1, "orMask": 0, "xorMask": 0 },
{ "type": "ACCOUNT_FLAGS", "target": "QbmBdAbvmXqCya8bia8WaD5izumKkC9BrY", "andMask": -1, "orMask": 0, "xorMask": 0 },
{ "type": "ACCOUNT_FLAGS", "target": "QSJ5cDLWivGcn9ym21azufBfiqeuGH1maq", "andMask": -1, "orMask": 0, "xorMask": 0 },
{ "type": "ACCOUNT_FLAGS", "target": "QhPXuFFRa9s91Q2qYKpSN5LVCUTqYkgRLz", "andMask": -1, "orMask": 0, "xorMask": 0 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QagyUZdmnKJA9LyEqcxJFFf2ehmcqVZsKb", "level": 5 },
{ "type": "ACCOUNT_LEVEL", "target": "QVhboSLD1VmX2YvAnfAXkbzvsmXkDJZTNR", "level": 5 },
{ "type": "ACCOUNT_LEVEL", "target": "Qg3TKLhPvn7bKVrT9x37wJiJ7YZ4jBuqQW", "level": 5 },
{ "type": "ACCOUNT_LEVEL", "target": "QcCYuXos5xBXXHbRg1RTfSdxiZEkGa3N2P", "level": 5 },
{ "type": "ACCOUNT_LEVEL", "target": "QPFM4xX2826MuBEhMtdReW1QR3vRYrQff3", "level": 5 },
{ "type": "ACCOUNT_LEVEL", "target": "QTVLRwoopfg7qSG9CMfCPJz3UydnT3jDxD", "level": 4 },
{ "type": "ACCOUNT_LEVEL", "target": "QPLoqpwAoytvpQKwvJ6GRsaRcVZ3xnYgVB", "level": 3 },
{ "type": "ACCOUNT_LEVEL", "target": "QVxGkDgXt4nHj4MAd1afV9AxT1XCUVLGja", "level": 3 },
{ "type": "ACCOUNT_LEVEL", "target": "QTrosCDj7oCdJc8K7sJZW6ssHU3StVoY7s", "level": 3 },
{ "type": "ACCOUNT_LEVEL", "target": "QeoFPT4xPxLp2P42yKVo22wx2V8kydfNmr", "level": 3 },
{ "type": "ACCOUNT_LEVEL", "target": "Qata5oApMShnD4F1kcgSJMTiYsxTPSFW4F", "level": 3 },
{ "type": "ACCOUNT_LEVEL", "target": "QXHmtFXzf4D7PEu73NfBm3sZyeuGrm3QC5", "level": 3 },
{ "type": "ACCOUNT_LEVEL", "target": "QRk5TG57SQGLkybXUqxBnobADTFGj9GR3Z", "level": 3 },
{ "type": "ACCOUNT_LEVEL", "target": "Qi7Lbvz1UdWgzgbKzfpRisLsdLR4smVoVh", "level": 3 },
Updated pre-launch blockchain config + fixes Fixed build timestamp parsing in Controller post reproducible build. Fixed REGISTER_NAME support in genesis block.
2020-01-24 11:35:30 +00:00
{ "type": "REWARD_SHARE", "minterPublicKey": "HFDmuc4HAAoVs9Siea3MugjBHasbotgVz2gsRDuLAAcB", "recipient": "QY82MasqEH6ChwXaETH4piMtE8Pk4NBWD3", "rewardSharePublicKey": "F35TbQXmgzz32cALj29jxzpdYSUKQvssqThLsZSabSXx", "sharePercent": 0 },
{ "type": "CREATE_GROUP", "creatorPublicKey": "CVancqfgb2vWLXHjqZF8LtoQyB7Y5HtZUrFKvtwrTkNW", "owner": "QbmBdAbvmXqCya8bia8WaD5izumKkC9BrY", "groupName": "dev-group", "description": "developer group", "isOpen": true, "approvalThreshold": "ONE", "minimumBlockDelay": 10, "maximumBlockDelay": 1440 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "JOIN_GROUP", "joinerPublicKey": "Gqcfa6YGXnKTr4F3QMpDQkjxxLGBmsq83wXcYeZvES7i", "groupId": 1 },
{ "type": "ADD_GROUP_ADMIN", "ownerPublicKey": "CVancqfgb2vWLXHjqZF8LtoQyB7Y5HtZUrFKvtwrTkNW", "groupId": 1, "member": "QTx98gU8ErigXkViWkvRH5JfaMpk8b3bHe" },
{ "type": "JOIN_GROUP", "joinerPublicKey": "2ZnSnZcpvMePw23f3AefANbRQHs7KjDyAyEzXc9dBMdn", "groupId": 1 },
{ "type": "ADD_GROUP_ADMIN", "ownerPublicKey": "CVancqfgb2vWLXHjqZF8LtoQyB7Y5HtZUrFKvtwrTkNW", "groupId": 1, "member": "QSJ5cDLWivGcn9ym21azufBfiqeuGH1maq" },
Updated pre-launch blockchain config + fixes Fixed build timestamp parsing in Controller post reproducible build. Fixed REGISTER_NAME support in genesis block.
2020-01-24 11:35:30 +00:00
{ "type": "JOIN_GROUP", "joinerPublicKey": "25jxnXz3xF3tK2WJHpUHwGx7DXR6yfjAHF1hFX5ice6H", "groupId": 1 },
{ "type": "ADD_GROUP_ADMIN", "ownerPublicKey": "CVancqfgb2vWLXHjqZF8LtoQyB7Y5HtZUrFKvtwrTkNW", "groupId": 1, "member": "QhPXuFFRa9s91Q2qYKpSN5LVCUTqYkgRLz" },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "UPDATE_GROUP", "ownerPublicKey": "CVancqfgb2vWLXHjqZF8LtoQyB7Y5HtZUrFKvtwrTkNW", "groupId": 1, "newOwner": "QUwGVHPPxJNJ2dq95abQNe79EyBN2K26zM", "newDescription": "developer group", "newIsOpen": false, "newApprovalThreshold": "PCT40", "minimumBlockDelay": 10, "maximumBlockDelay": 1440 },
ProxyForging->RewardShare massive refactor & more... 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!
2019-10-29 17:46:55 +00:00
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QVLuvt9krmxXwQPAeAhxzhuMF5i8F4aNs8", "level": 5 },
Update blockchain.json to nearer launch version
2019-11-12 15:04:41 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "Qe9VPzQp3h4Kg3DHSHBUQ3AM3AiRBfCDfX", "level": 5 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QcrnYL6yNwHKuEzYLXQ8LewG3m2B5k9K5f", "level": 5 },
Update blockchain.json to nearer launch version
2019-11-12 15:04:41 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QPYfRd1uhnAgqkZNmjNCjgPhkguMnHWuc4", "level": 5 },
{ "type": "ACCOUNT_LEVEL", "target": "QM9zVbXXnfrtQ1X7zPQ5zxPYPAWTaVMXqZ", "level": 5 },
{ "type": "ACCOUNT_LEVEL", "target": "Qft1ktvJ14eBFjpJaphT24ks4WRcN3K6tB", "level": 5 },
{ "type": "ACCOUNT_LEVEL", "target": "QcHF9YogbuzZhG4fK4116pgE2qrmbkGh2n", "level": 5 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QaUciVnbQDXdNygJadEY31PuDEBLi6Spmu", "level": 5 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QWe1iPDudLU189BggPykbH1DrAeaFEgX6W", "level": 5 },
Update blockchain.json to nearer launch version
2019-11-12 15:04:41 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QgECFJiiri2dDN4zA32URvbdDid2cFrJwM", "level": 5 },
{ "type": "ACCOUNT_LEVEL", "target": "QTTrv8SWR8huV8TFYUEQhfZ1j1JmtL5p8G", "level": 5 },
Updated pre-launch blockchain config. Smaller splash graphic.
2019-12-23 15:09:45 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QYgVi26jUqMzJo4ahZV9yekQNnYKHBaX8r", "level": 5 },
Update blockchain.json to nearer launch version
2019-11-12 15:04:41 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QXan6JJ1WuRi7GigvFDjtTzJY1rfYEqEqv", "level": 5 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QQa3MTgdnru5B7wSqPcq7qXcZcpbDQ7oyE", "level": 5 },
{ "type": "ACCOUNT_LEVEL", "target": "QQoHo1x4hvZcSFbj2uQAXQhq2ZXBUgPeNj", "level": 5 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QUvoLFfkuVuRe1KGMLQS4nUHry6CBTuTYz", "level": 5 },
Updated pre-launch blockchain config. Smaller splash graphic.
2019-12-23 15:09:45 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QTEE4ZJXv68ke4841HWjTLAAU8mfccxwbE", "level": 5 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QQEZEGWt3sAPwEWYD2RQ6tMwnpkayG81dY", "level": 5 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QVurebcEbe4USR4xcS3Mbk12mhxsjRX31u", "level": 5 },
Update blockchain.json to nearer launch version
2019-11-12 15:04:41 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QfmM8dgfikTB2FYVuJ9owzQXVm8wP7T4QT", "level": 5 },
{ "type": "ACCOUNT_LEVEL", "target": "QPUMyJ59kkrp75tDzDPxSyw1GWCrbC2cS2", "level": 5 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "Qc9dZchoYfc1eRJhSLXR9rxSHcqNB47Dex", "level": 5 },
{ "type": "ACCOUNT_LEVEL", "target": "QTMTFswUU83XVmk6T4Gez7qUJCccbAad7S", "level": 5 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QjrC8NXwR8gFkEauvRwCPxqHroPFqAJbhK", "level": 5 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QPcTWoAhYWmwjmWbQAS8muisrQVaLJMbg7", "level": 5 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QgpAW6uqwNR58gNYWRCVXNLm4F5TuckAw4", "level": 5 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QLpLY9o3X21q7q4L6u5JdDuMskYA838iYE", "level": 5 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QWpJxitn53ovwknQfrCaqivvoUNuPrX2sb", "level": 5 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QdGbhtkFHUqd9nK9UegxxGXD1eSRYSoKjt", "level": 5 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QXv4WiqgryFPi8BgX7RU7gqtAgrVutmU4S", "level": 5 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QP8xG56L8b28h1mguSk9LuzNhxbHgAoL9b", "level": 5 },
{ "type": "ACCOUNT_LEVEL", "target": "QfjL32jLsxtumbfx6ufmfCFCBccVCQFkrh", "level": 5 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QguNJ4evpN9i76dYHysTzLiKoWKFhE4B4U", "level": 5 },
{ "type": "ACCOUNT_LEVEL", "target": "QSkiGy3v3MwvGy3aACuyLDv3Xy2AWAYfPS", "level": 5 },
Updated pre-launch blockchain config. Smaller splash graphic.
2019-12-23 15:09:45 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QbwgBD6LWdk1hZsb8EwdVVmDZdvpxMzyGT", "level": 5 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "Qbcy4uyMkQF2JXYqGkueDiFNZ4tHjRg8CR", "level": 5 },
Updated pre-launch blockchain config. Smaller splash graphic.
2019-12-23 15:09:45 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QdXe21sjY8smjVmiAUgZY8xWVzwgxMgK5A", "level": 5 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QawB5MesBratjs2d9EMnXnrN4EC7gw7LRw", "level": 5 },
{ "type": "ACCOUNT_LEVEL", "target": "QPEbvVBWDG7qgy4smY8nWiie78Vec8qiT9", "level": 5 },
{ "type": "ACCOUNT_LEVEL", "target": "QXKmtkHHwaUQzGeHHG2dFiHUnKAp815Mzq", "level": 5 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QZkThgFfExognAbxLjYZGVHpL7X6g3EG4A", "level": 4 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QbH8srDKeS5VcsQsgsaF3nqCzGT1NqfsTx", "level": 4 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QWLpsGYrkF2cy3tH6DCxso7kXZpZJvv13e", "level": 4 },
Updated pre-launch blockchain config. Smaller splash graphic.
2019-12-23 15:09:45 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QdtAQm1EGNgM7QDSaC2qvV9WdpRHwpApUT", "level": 4 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QbqRyFw7Xu6Nsb4FraaUSe7nUPukuUpekG", "level": 4 },
Update blockchain.json to nearer launch version
2019-11-12 15:04:41 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QRFHr4jnVgvAsPTubeSrh8bPy1yzwzYaWD", "level": 4 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QWuW2YMygVtWieUo6a4yayD1xFDWdnmo5j", "level": 4 },
{ "type": "ACCOUNT_LEVEL", "target": "QVkQTr8PzDTaNxhvrC47UUxUi6V987a5qL", "level": 4 },
{ "type": "ACCOUNT_LEVEL", "target": "QQPYyoE3Bm2vh8Wr5aaBNyirC8dd3BhBGH", "level": 4 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QUzUCfoakDqBaL5zBgfvTKLHcuxbUfB38Q", "level": 4 },
{ "type": "ACCOUNT_LEVEL", "target": "QSBJuNoCAFUTcevuCTcMi3i5nzNPhC5R4b", "level": 4 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QTGeQqn3XEFdnnCqvifCFXYdKym7SaHzTd", "level": 4 },
{ "type": "ACCOUNT_LEVEL", "target": "QVSqUrNFR4mPTMa7UdVmNKZTSaDVAv8XXF", "level": 4 },
{ "type": "ACCOUNT_LEVEL", "target": "QMLjFiPiPa46YBRoushe6a227kSrXnXyKb", "level": 4 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QNJ8jDx6Mni2GKLHEY1BMh9xDumT3vnJQM", "level": 4 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QgVZb632eqF1eLQm9gBGuBtyp9Dyz2FKUK", "level": 4 },
{ "type": "ACCOUNT_LEVEL", "target": "QPREQjU2defiYdgA33HDiLNGBpxtuebeqE", "level": 4 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QiBYApdEYRwsFYjt59UJqZV55wcwykvhsh", "level": 4 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QMsKXQAYKmR7dBH4P3kMLiKzYatK3h1CeS", "level": 4 },
{ "type": "ACCOUNT_LEVEL", "target": "QRCtc67FTNKS5zVXM8omw8F55h9DP7herL", "level": 4 },
Updated pre-launch blockchain config. Smaller splash graphic.
2019-12-23 15:09:45 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QZvHW7amu5DNktsBgaMrR1brHZhhhVwKLW", "level": 4 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QgqM5bKs3tNqKNAnVeaQp4oaYMXCmX6YJr", "level": 4 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QhMEWhZCufhKLkfuNU2DAzj1mmWoAxX147", "level": 4 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QbvxC3ENqomXp11833APchdjeyCNd49nLj", "level": 4 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "Qj5ncwncQY4KPYgKHD1eYpXHbR717PeLcJ", "level": 4 },
{ "type": "ACCOUNT_LEVEL", "target": "QY1RFZTD2ogRohf3UrdT4g1Qo9D122AZDN", "level": 4 },
{ "type": "ACCOUNT_LEVEL", "target": "QcU4VhU9ohDXU4k4AUMapgJRYSzEpizjLN", "level": 4 },
{ "type": "ACCOUNT_LEVEL", "target": "QZsygC1chppsJK1cnaHG4fEsNaDYfLF7ZJ", "level": 4 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QYGcPZcRhGaY1MsiDr3VtwTXmB9TAbLFSn", "level": 4 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "Qgwb5SLVGAperXAMoVNBDvGpVAxTVY7f6F", "level": 4 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QaFN7DWcGF7keNACJpwCVnegePbfsAoFCw", "level": 4 },
{ "type": "ACCOUNT_LEVEL", "target": "QYGNMWBmqWgVtMWGHypAsKhDVQw5mrFZww", "level": 4 },
Updated pre-launch blockchain config. Smaller splash graphic.
2019-12-23 15:09:45 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QcNmqT8CZ6zSZwuRm5LahRZnuGBJRnPY8o", "level": 4 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QRKRk5HVADsN1LHygK7q2pA7dWnYKnPpCT", "level": 4 },
{ "type": "ACCOUNT_LEVEL", "target": "QSGB4Rd2xhd6UmA9LALTQ4f89Tfsz5VajU", "level": 4 },
{ "type": "ACCOUNT_LEVEL", "target": "QNVKrjEq5bZdiDtgo64m5kz87rTHqCwvCP", "level": 4 },
{ "type": "ACCOUNT_LEVEL", "target": "QNMDKE7XTujNQkuQorcHXw6hL7qRvyaTjr", "level": 4 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QgCQq4cFaGrJhwvKs4XwvccKiLZ8GVMCXR", "level": 4 },
{ "type": "ACCOUNT_LEVEL", "target": "QRtRELSSASzqiYy2FtNcrePH6TVnqJkv9B", "level": 4 },
{ "type": "ACCOUNT_LEVEL", "target": "QMtm8wVPHGE3qHg2hMaj6SZ78D5eXw3VWZ", "level": 4 },
{ "type": "ACCOUNT_LEVEL", "target": "QY6ZGZdi8h5op2VrRXkG1W5Jp3feLwp7ZD", "level": 3 },
{ "type": "ACCOUNT_LEVEL", "target": "QVrvy4ac2jBTfxyCKB7MLimqJooTDBApmS", "level": 3 },
{ "type": "ACCOUNT_LEVEL", "target": "QcCBVfL35rxSyQ416L2MBz14FYbNrbeNPx", "level": 3 },
Updated pre-launch blockchain config. Smaller splash graphic.
2019-12-23 15:09:45 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QNHdGeFJmPcDdN8prPzPL4bk2dpnJ2ZZFr", "level": 3 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QRWEbcRnLoGccAndtLcGgpeQFH2ZBcMqHo", "level": 3 },
Updated pre-launch blockchain config. Smaller splash graphic.
2019-12-23 15:09:45 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "Qce2Djqrk2WzG1QhMZ3BqFok9HGsz4wtM3", "level": 3 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QUXga5K8nzd9EqYtvEesZWEYuA688h6D3d", "level": 3 },
{ "type": "ACCOUNT_LEVEL", "target": "QfbX8JJupEw5ckNtU4upQgET35oLTr5e6v", "level": 3 },
{ "type": "ACCOUNT_LEVEL", "target": "QRaDef6H2zYfefqLwYGmUg7T6DAqo6DDqc", "level": 3 },
{ "type": "ACCOUNT_LEVEL", "target": "QibuD4c6gvXgS4iut7q3sXuVb23rgFJq2M", "level": 3 },
Updated pre-launch blockchain config. Smaller splash graphic.
2019-12-23 15:09:45 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QMozpRT9aUunfmPh7EtQ6LPoth2JFJWBXC", "level": 3 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QTpYQqRyMekaEuECziirzy3HvCVofZS1wJ", "level": 3 },
{ "type": "ACCOUNT_LEVEL", "target": "QawSgZ7i2LLFTKyPxQptk9gN526ihy5yZi", "level": 3 },
{ "type": "ACCOUNT_LEVEL", "target": "QMuWNAJ2tbeViHtBUN3yD2KARrrzcanLAd", "level": 3 },
{ "type": "ACCOUNT_LEVEL", "target": "QUGo9SErgc6ceB5aBzcSJDNqBkQ9eaCKZS", "level": 3 },
{ "type": "ACCOUNT_LEVEL", "target": "QdFZk74skMUu4rKMPEmcSVwR87LNDe6o3Y", "level": 3 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "Qgp16aMcdiS2EUkxCm5NSZgB8DixGK51zT", "level": 3 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QScBgSw74MquesXmVJxerX3YgyhtShRr4q", "level": 3 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QgcF6KgVZ9eDAMHJdSEeAtp91t931VKZMv", "level": 3 },
{ "type": "ACCOUNT_LEVEL", "target": "QjgGeEkyiXa43pyqkXxZbvAChQpVYfUyKz", "level": 3 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QRWEbzH4niUcu9dL3Yq42X4j89aqQk3qWw", "level": 3 },
{ "type": "ACCOUNT_LEVEL", "target": "QYD3kXchZ86vUyJBXNCVQ4LUvTAd6PUZW3", "level": 3 },
Updated pre-launch blockchain config. Smaller splash graphic.
2019-12-23 15:09:45 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QPqfuZpmyA6cK6WUFwcGeKH2Te1aegkHBM", "level": 3 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QhQdzLn36SDgrgoMfvdZAkoWtTUHpB3acJ", "level": 3 },
{ "type": "ACCOUNT_LEVEL", "target": "QWL7kZp6Pdd1bhxZ6SXPhVf5g7GParG9CC", "level": 3 },
{ "type": "ACCOUNT_LEVEL", "target": "QbxJvwrEHZs7MDE8rbqBwZAZkcywue5F3W", "level": 3 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QUKKwug9PNai3DBggXUXP8Ag7WmR5SVUR4", "level": 3 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QWwrtjBL4ah965XPXHYJhymreC9jyryNLZ", "level": 3 },
{ "type": "ACCOUNT_LEVEL", "target": "QjEaMxcBKMsj91ytKe6GdTBJP8Mu1Ru3r4", "level": 3 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QeDhJRqTyeDmcgGJoms6FHK49ZGVpVahxg", "level": 3 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QbYTowTHCr9WzfrR6b8uDfJKwL41nG1vyr", "level": 3 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QPusqAVBVFGAAeE7RdospttA18AuyLP7sB", "level": 3 },
{ "type": "ACCOUNT_LEVEL", "target": "Qd1Px9vhWuEmF2SbLx3Ez7HhGtifGMa8TJ", "level": 3 },
{ "type": "ACCOUNT_LEVEL", "target": "QSq8y4ZrSbF55ZddWNcw1ett2LDtjQEvNn", "level": 3 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QNw9xAm9TUerin9QsapCPL9mV6zmoXyJrh", "level": 3 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QU8XJyQEZxSHgrS1XyooWUo5MmruXg36Pe", "level": 3 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QYuMATkLjz7YB6s4EG1aWCmmmrAPj3W9Ce", "level": 3 },
{ "type": "ACCOUNT_LEVEL", "target": "QNiTnonHpXTeUrgNdyYWVDPP4ZdjkLpW72", "level": 3 },
Updated pre-launch blockchain config. Smaller splash graphic.
2019-12-23 15:09:45 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QTtXS6fZGThRLq4qgkwM4ngBYkLoFyZ3bK", "level": 3 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QjrCFCi6dqvka4UELg2SHhM2oWnQWepd1o", "level": 3 },
{ "type": "ACCOUNT_LEVEL", "target": "QREtYDhP4HkpeCCZroemuGXMGVFoZHH3Lp", "level": 3 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QgesuKa3zwx8VAseF1oHZAFHMf29k8ergq", "level": 2 },
Updated pre-launch blockchain config. Smaller splash graphic.
2019-12-23 15:09:45 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QdXdUxnyKGGo7eEfTcx85oEikNe5nYnuwa", "level": 2 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QWBFK5h61ZxGfqQpEkwwKTcLAo8t9VWe4K", "level": 2 },
{ "type": "ACCOUNT_LEVEL", "target": "QjEAs2or122weKppv5zALzoQzXxbsDjy3f", "level": 2 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QZ19JRpSsgvm4z6EjnbhdxJBoUYzDGvP3x", "level": 2 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QUZQPWhrxpze32vGiux6wa85kg9iwuhCDx", "level": 2 },
{ "type": "ACCOUNT_LEVEL", "target": "QdwSxr3t4hdGHjQFy6EVGR9yGMipefsTuo", "level": 2 },
{ "type": "ACCOUNT_LEVEL", "target": "QZ2gi6BhUNpGmrErgJLFuY1WHy6xK1J7qX", "level": 2 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QWinRb65f2g3yBoaZvTrQKQk7CW7vfBgGX", "level": 2 },
{ "type": "ACCOUNT_LEVEL", "target": "QQaKBSjAt9RK2bqJoSriR77X4ULstGzrFQ", "level": 2 },
{ "type": "ACCOUNT_LEVEL", "target": "QisSQZ7Et7Rfzx2SCC2o9UDSeRZWMyFKWc", "level": 2 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QXYk68x2tiUrDBv8eq6wd4KtBmLHYiC4zR", "level": 2 },
{ "type": "ACCOUNT_LEVEL", "target": "QTyokTJrR4b2y76An3BFUEbqQy5vvg76iN", "level": 2 },
{ "type": "ACCOUNT_LEVEL", "target": "QPyx2bNiAnJEjitfeAh8jZXzQVKio2B7Mi", "level": 2 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QMJwdufHY9dMoARHCUyGbMPAqUB4BcqGKm", "level": 2 },
{ "type": "ACCOUNT_LEVEL", "target": "QNffmqjCUQsLaHLZXBaA47tQW7bERdpP4R", "level": 2 },
Updated pre-launch blockchain config. Smaller splash graphic.
2019-12-23 15:09:45 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QeUc5NfzubZD4eA4eJ7bfXAFraAWc7jVz5", "level": 2 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QfPcwetW3BErP4ySTurxFJSHpNkNXPEhGk", "level": 2 },
Update blockchain.json to nearer launch version
2019-11-12 15:04:41 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QQHWFSJpzuDupPfcTvGMRNJp2UGz98Kb7j", "level": 2 },
{ "type": "ACCOUNT_LEVEL", "target": "QdepeWWLMD3LiDRKkKBria29rDhZP9V5RJ", "level": 2 },
Updated pre-launch blockchain config. Smaller splash graphic.
2019-12-23 15:09:45 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QeSh3t1AnaRcRThkkUTvvdMEouixCADeVh", "level": 2 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QMMh94Pfs5LVE4xJee1yggViqP1YDdQHT4", "level": 2 },
Update blockchain.json to nearer launch version
2019-11-12 15:04:41 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QWez1VBfYVJ8KFoZ6MhJDzYVLbn5mr38VT", "level": 2 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QZiYh4m4Uh3FH52cnow8MrNyXhSH88bp2H", "level": 2 },
Update blockchain.json to nearer launch version
2019-11-12 15:04:41 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QYsh2NB6TogqV1iXHmHXcVaWw25WEYA94o", "level": 2 },
{ "type": "ACCOUNT_LEVEL", "target": "QU9dnN47Nc5KaH7JwNoCZ7TANwCW5VX9iG", "level": 2 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QZjCgcSVvSRsFZeLJz9C5dTa36s3cSKqvB", "level": 2 },
Update blockchain.json to nearer launch version
2019-11-12 15:04:41 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QXoW5M113C3SDUeFdjVVs2m1RT9XtzXS3z", "level": 2 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QfhJM5CpX5MhfjCcopwfw7pgS6w1hVJ49E", "level": 2 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QjsD7pMh2LpmgYudaaRM8gmzhBC4c9uwyj", "level": 2 },
Update blockchain.json to nearer launch version
2019-11-12 15:04:41 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QZxcntxfJimHus9pgfvVVPbpHs5yU7ZMhB", "level": 2 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QRBVE5gHumH6RUgEUxJdQ5417NUvc14k3F", "level": 2 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QakZtV3nZeRp5UEoEUNX7p8Qz5VbVXTQid", "level": 2 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QXeiJa7ftN6dAYNZcdqKDBhmAFyGjX2zkm", "level": 2 },
{ "type": "ACCOUNT_LEVEL", "target": "Qc2eRuYXtpATrg87Pr1WDXkUBCsgNRYcQF", "level": 2 },
{ "type": "ACCOUNT_LEVEL", "target": "QbEJ5tfeskASVnmLFeKzspuZJJb6cJVPZ4", "level": 2 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QYpYshfVzMMVU71KqAV4erX3NJAUCnJXgD", "level": 2 },
{ "type": "ACCOUNT_LEVEL", "target": "QViKVZa3M3ar7RBRSBMTx8FdzLh1zxUhN8", "level": 2 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QWvTdm9LU1GSX9q6Rrvgx7xjo2iuV2Gxn1", "level": 2 },
{ "type": "ACCOUNT_LEVEL", "target": "QZw7tgMttSySNMKfcMrEbdtnqHVrQ9w9fT", "level": 2 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QbGwYRV3UDek4VNpzoAVVQWfoKjZmm4qPb", "level": 1 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QYM76r3tuf6FJWz2USqVjwXJrV9tLMz1cj", "level": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QfnbnWrRQ4HNDQvtg3wG2B1eC4ycUsFqZz", "level": 1 },
Update blockchain.json to nearer launch version
2019-11-12 15:04:41 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QUdjqijDoyc83K4WcMW1sCn7zLd2t1WTqn", "level": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QRUbzEbLd7fRjAx2fBdXAH4QS1WQyetvDc", "level": 1 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QU9K6pWhkok9mokkPDoCwgSu3j62ECuKLD", "level": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QaZs97g4Mbq9tXMoBWbhw3jFvBBVkWKS5F", "level": 1 },
{ "type": "ACCOUNT_LEVEL", "target": "QcJwVCyzraPy51uB4xd4f94n2UFYAsznGC", "level": 1 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QMb2cAKb2BUxknneuoXQynJ7uzosJ57Top", "level": 1 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QZbKMgYBwWGyTDJzoDir2aNqXsFdDp6fS9", "level": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QZ7wvWAUcHKRhvQ3ijdrqM4zucQKCgQ1hQ", "level": 1 },
Updated pre-launch blockchain config. Smaller splash graphic.
2019-12-23 15:09:45 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QgmEtScSZWJmTUAidCZKj6gDr3LznZ6rr4", "level": 1 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QVuksgNt3QAr7KCrkxtE5FWrczfgLKxs4H", "level": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QQXgH4CnQCB76BbXhsApu6ShhohFfvoXv7", "level": 1 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QQzMut6erjgSKCpZ1dHDcjKcj9KAce7cug", "level": 1 },
Updated pre-launch blockchain config. Smaller splash graphic.
2019-12-23 15:09:45 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QZJc1V32oFm8tufB4bk7fa3aepu4EdkeDU", "level": 1 },
{ "type": "ACCOUNT_LEVEL", "target": "QSkicapNH35a3UebSxxSMCfntBhwwi6veW", "level": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QLqZD8eiNk8nrzyWcURfQDS9T5NWx98vrz", "level": 1 },
Update blockchain.json to nearer launch version
2019-11-12 15:04:41 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QVEfMEeEHP768c9rEyi3WcH2JQwqheVDe3", "level": 1 },
{ "type": "ACCOUNT_LEVEL", "target": "QehM6hQZVkrYAst8WrBVdQiMFfTtDtbKQu", "level": 1 },
{ "type": "ACCOUNT_LEVEL", "target": "QY7gQwZKiPYMHYjYASSDBhhAoyYaxmex17", "level": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QPE3EGR8LTYSLtWBq52SFte66oud6cxchF", "level": 1 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "Qa9NXeLAvmaTsKackfDRmm1A9zy7JeEjgV", "level": 1 },
Update blockchain.json to nearer launch version
2019-11-12 15:04:41 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QXqAtZJsLU6HFGTzuegjeUbmEW8cGEnYt6", "level": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QXpCzKnANyh8jrRRxemvsXHAeFRHrDvdXF", "level": 1 },
Updated pre-launch blockchain config. Smaller splash graphic.
2019-12-23 15:09:45 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "Qd1Xw41BzN1CgASqsh2PcrrkTKyDs2MVYF", "level": 1 },
Update blockchain.json to nearer launch version
2019-11-12 15:04:41 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QVb7P596imucSwDqb5HHEjqpnAre615PbS", "level": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QTgfJFaEj5wuFvufwjUmYPhQ8eVfHR4u22", "level": 1 },
Update blockchain.json to nearer launch version
2019-11-12 15:04:41 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QNMtHRjEWPgZUVCpiC2qE2LyJsxq1BC1Yj", "level": 1 },
{ "type": "ACCOUNT_LEVEL", "target": "QUNTxxwr9f47RcwY48ZUP6FmmKnWCsxes5", "level": 1 },
{ "type": "ACCOUNT_LEVEL", "target": "QSTDdguUfKe6TaQrik2zq4Xrbu6unxNa9o", "level": 1 },
{ "type": "ACCOUNT_LEVEL", "target": "QgsxpySDm1qja6D2EyKuHPiUhyTM1RMk6c", "level": 1 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QgJDnJF1zfoFBxB1LRvi5Rxb8p345UmVos", "level": 1 },
Update blockchain.json to nearer launch version
2019-11-12 15:04:41 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QWZwi5NUzHuJfg5fh9HzjWRpQc1fmMknAh", "level": 1 },
{ "type": "ACCOUNT_LEVEL", "target": "QP9vU5yTsBjuTSFxH5Cb9VXYNRHKhMNAJ4", "level": 1 },
{ "type": "ACCOUNT_LEVEL", "target": "QXm5e16Lq6dnYwpZJ8Rn2cME3ziHZfRRnp", "level": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QWkLaA4fYK51m4CszSgBd7efoDsSKamdf1", "level": 1 },
{ "type": "ACCOUNT_LEVEL", "target": "QZgDpQ1Vyi5pNNe2ZzBRhcUgSU13yeWvmH", "level": 1 },
Update blockchain.json to nearer launch version
2019-11-12 15:04:41 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QiQernJdiP4zCECB93v247FUtovkfJyTYm", "level": 1 },
{ "type": "ACCOUNT_LEVEL", "target": "Qa4KygekpW1Brr3D66K6rGtS5AY8qkhvD3", "level": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "ACCOUNT_LEVEL", "target": "QQfFiVWkyAmfs1hDUcWU6XBfonxLdz6RSN", "level": 1 },
Update blockchain.json to nearer launch version
2019-11-12 15:04:41 +00:00
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "GENESIS", "recipient": "QS2k8PMpmvUHzFDp2JfbVxRo8SiGiV72xx", "amount": "637557960.49687541", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QUM95jekFMye3Lmkg2gj7CdhFreYye4DaA", "amount": "400671036.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QaYAUoT2SzYA6kqBEW6W11brkYpSf7g4Wy", "amount": "352652351.30705076", "assetId": 1 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "GENESIS", "recipient": "QdoLZqB3pY4NgbSpvbsFzBDq2LcShjXsoq", "amount": "263574650.00000000", "assetId": 1 },
Updated pre-launch blockchain config. Smaller splash graphic.
2019-12-23 15:09:45 +00:00
{ "type": "GENESIS", "recipient": "QTnPQVphizFhBFtSbTQzAC4Kubj4uqpv96", "amount": "232356835.62157121", "assetId": 1 },
Higher account levels more likely to win blocks Also: RewardShareKeys app now supports only one arg (minter private key) in self-reward-share mode, where recipient public key is derived from minter private key. Added methods to Account for returning 'effective' minting level where minting level for founders is read from blockchain config. (Or returns zero if unable to mint). Changed two Block constructors into static methods that return a new Block as there was way too much work being done to really be called a constructor, especially with all the opportunities to throw an exception too. Main blockchain config updated to reflect near-launch version. Added/changed blockchain weight tests to check block winning based on higher account levels.
2019-11-06 09:47:10 +00:00
{ "type": "GENESIS", "recipient": "QMtx2UmUuRZckCmRJRyxdzSAazHP8hU5rA", "amount": "160672815.43629771", "assetId": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "GENESIS", "recipient": "QVz1rKM9QQrGX7gkxR9EV8a2T4AuD1QT87", "amount": "128506517.58266672", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QUUcETWLi7EcjQ9M83Aur3SwmESFBFuQye", "amount": "126998534.24906898", "assetId": 1 },
{ "type": "GENESIS", "recipient": "Qa15fMdEiY7WqK2xwvdHrdhU2TE6yk3V3L", "amount": "122690068.33700012", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QM4LF9EzQnXJ9VyFwnJbJzskJLrybuSzsw", "amount": "114361793.00000000", "assetId": 1 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "GENESIS", "recipient": "QQKeokRiFCgAhBSdu1DUf5e1LCkgApvrxZ", "amount": "100000078.00000000", "assetId": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "GENESIS", "recipient": "QiaaoNZ54wKoaUMXxW72UsPt1MiPpeUTWm", "amount": "100000031.00000000", "assetId": 1 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "GENESIS", "recipient": "QYoRWAxw6CVMeYeWHKJh3csmTVkVzjpdBo", "amount": "100000026.00000000", "assetId": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "GENESIS", "recipient": "QPwLkxemtGsrdcPJSA4iMgKbBPdecL7dwZ", "amount": "99999999.00000000", "assetId": 1 },
Higher account levels more likely to win blocks Also: RewardShareKeys app now supports only one arg (minter private key) in self-reward-share mode, where recipient public key is derived from minter private key. Added methods to Account for returning 'effective' minting level where minting level for founders is read from blockchain config. (Or returns zero if unable to mint). Changed two Block constructors into static methods that return a new Block as there was way too much work being done to really be called a constructor, especially with all the opportunities to throw an exception too. Main blockchain config updated to reflect near-launch version. Added/changed blockchain weight tests to check block winning based on higher account levels.
2019-11-06 09:47:10 +00:00
{ "type": "GENESIS", "recipient": "QMkgf9Y6Ac2TUrynDvyhX69ekpC3P3GQmN", "amount": "99008835.47860426", "assetId": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "GENESIS", "recipient": "QUnfm6t9SrhgFB8YqCV1vQhmqFzhncxioK", "amount": "80000207.00000000", "assetId": 1 },
Higher account levels more likely to win blocks Also: RewardShareKeys app now supports only one arg (minter private key) in self-reward-share mode, where recipient public key is derived from minter private key. Added methods to Account for returning 'effective' minting level where minting level for founders is read from blockchain config. (Or returns zero if unable to mint). Changed two Block constructors into static methods that return a new Block as there was way too much work being done to really be called a constructor, especially with all the opportunities to throw an exception too. Main blockchain config updated to reflect near-launch version. Added/changed blockchain weight tests to check block winning based on higher account levels.
2019-11-06 09:47:10 +00:00
{ "type": "GENESIS", "recipient": "QWZm17rRXeUehcM4TprVNNRSTHWQmG2bME", "amount": "62663714.00000000", "assetId": 1 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "GENESIS", "recipient": "QMWSbqWDC1eHU7fCGJ3UwABHiTxBgBJGRC", "amount": "60036435.28601510", "assetId": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "GENESIS", "recipient": "QXdcbgN6vdQRBKJzHSB2JaSDDzPEsTUi14", "amount": "49450000.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QczMrVLEnEAXwvucwrfasH9H7QHNMPxLKu", "amount": "46488501.53473695", "assetId": 1 },
Updated pre-launch blockchain config. Smaller splash graphic.
2019-12-23 15:09:45 +00:00
{ "type": "GENESIS", "recipient": "Qaa5hs9dj1gPxhqigH7tVyZ3oRuVcMULXB", "amount": "44766868.70000000", "assetId": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "GENESIS", "recipient": "QQMswzmv65MZSdafqzCACm3tbLj23ixkVR", "amount": "42447489.00000000", "assetId": 1 },
Higher account levels more likely to win blocks Also: RewardShareKeys app now supports only one arg (minter private key) in self-reward-share mode, where recipient public key is derived from minter private key. Added methods to Account for returning 'effective' minting level where minting level for founders is read from blockchain config. (Or returns zero if unable to mint). Changed two Block constructors into static methods that return a new Block as there was way too much work being done to really be called a constructor, especially with all the opportunities to throw an exception too. Main blockchain config updated to reflect near-launch version. Added/changed blockchain weight tests to check block winning based on higher account levels.
2019-11-06 09:47:10 +00:00
{ "type": "GENESIS", "recipient": "Qa95hURaNK4kPhDhbdmDFm2wMkkoWFZ4Zz", "amount": "40976709.97984710", "assetId": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "GENESIS", "recipient": "QVEde9kJt2ejqXavBzK35zY3eztnkSXTwN", "amount": "38172492.00000000", "assetId": 1 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "GENESIS", "recipient": "QZjDFrMrgeR9SGL8bprqyiXVtAZMVCXESZ", "amount": "37291276.42323117", "assetId": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "GENESIS", "recipient": "QPmmPjdDXW35ykF557KbaVy5jYBbaM3pRp", "amount": "33333332.00000000", "assetId": 1 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "GENESIS", "recipient": "QaWReiLe5tAsTNoq7hMiSGNasJEXTX5bmn", "amount": "31465829.00562504", "assetId": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "GENESIS", "recipient": "QLrErVJvpRdYAt4dGwk8i8rG3PMUSgpp3i", "amount": "26593505.67231102", "assetId": 1 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "GENESIS", "recipient": "QYsLsfwMRBPnunmuWmFkM4hvGsfooY8ssU", "amount": "25303386.66951814", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QgULJXk3qyLDr4EKkz48rxwwvWK7BDL8Ux", "amount": "22476856.86000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QNwedkYs6hToBRPZvBb6naKvDEgB7BeaKi", "amount": "21967101.30582773", "assetId": 1 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "GENESIS", "recipient": "QQ2DsD3fKWy88dQ6PMmdaNkAwSQrGof9aX", "amount": "20555555.00000000", "assetId": 1 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "GENESIS", "recipient": "QgP7vQABSDJwuE8VTdVkiNnbkorqWWctQm", "amount": "20442665.63310002", "assetId": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "GENESIS", "recipient": "QM5Fg3kBzj9BqsGAJKHhsEtgRgf4x2Yn5G", "amount": "20000006.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QLdC7wm9PYC1KjgZaeVdGzH4M88BYhEeEw", "amount": "19927901.00000000", "assetId": 1 },
Update blockchain.json to nearer launch version
2019-11-12 15:04:41 +00:00
{ "type": "GENESIS", "recipient": "QLgBTDkt7t7WwbTd1RM8iGxu9FexPZcn7C", "amount": "19000025.40000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QQShonrAdJXg4CzhegtynzaBP7S631vKGq", "amount": "16577946.00000000", "assetId": 1 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "GENESIS", "recipient": "QM5gE4YYAL6byjpbbGH26TvuCUPmjcksY9", "amount": "16000000.00000000", "assetId": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "GENESIS", "recipient": "QMFJGxGLCbegHL3NZ7HRo3UYaCXhweJVKS", "amount": "14977498.00000000", "assetId": 1 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "GENESIS", "recipient": "QcAVj3i3drVkiC9P8FtDgVdYz8Zeu61uNg", "amount": "13142764.62938834", "assetId": 1 },
Updated pre-launch blockchain config. Smaller splash graphic.
2019-12-23 15:09:45 +00:00
{ "type": "GENESIS", "recipient": "QTDB2mmxEU7L4oUnmBh9F3qhCxfVpJUzaA", "amount": "12960806.75574690", "assetId": 1 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "GENESIS", "recipient": "QLgewDr48AZxWbDbRZ12xEvCePwPj9bMBE", "amount": "12684967.00000000", "assetId": 1 },
Higher account levels more likely to win blocks Also: RewardShareKeys app now supports only one arg (minter private key) in self-reward-share mode, where recipient public key is derived from minter private key. Added methods to Account for returning 'effective' minting level where minting level for founders is read from blockchain config. (Or returns zero if unable to mint). Changed two Block constructors into static methods that return a new Block as there was way too much work being done to really be called a constructor, especially with all the opportunities to throw an exception too. Main blockchain config updated to reflect near-launch version. Added/changed blockchain weight tests to check block winning based on higher account levels.
2019-11-06 09:47:10 +00:00
{ "type": "GENESIS", "recipient": "QPEoMF2dA7NHrHhsSG9zczCFwx9wFdWvzT", "amount": "10033147.61257500", "assetId": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "GENESIS", "recipient": "QQSiZAgdMjadXZRVTHa252AAY2yjZfQKR1", "amount": "10000000.00000000", "assetId": 1 },
Updated pre-launch blockchain config. Smaller splash graphic.
2019-12-23 15:09:45 +00:00
{ "type": "GENESIS", "recipient": "QWLhUT55hZHgdD7ayEqwHnF9h62dHV45G1", "amount": "9999999.00000000", "assetId": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "GENESIS", "recipient": "QjnHejJPyuyTRs7huzcqXtbM6sufWyLf9o", "amount": "9999999.00000000", "assetId": 1 },
Higher account levels more likely to win blocks Also: RewardShareKeys app now supports only one arg (minter private key) in self-reward-share mode, where recipient public key is derived from minter private key. Added methods to Account for returning 'effective' minting level where minting level for founders is read from blockchain config. (Or returns zero if unable to mint). Changed two Block constructors into static methods that return a new Block as there was way too much work being done to really be called a constructor, especially with all the opportunities to throw an exception too. Main blockchain config updated to reflect near-launch version. Added/changed blockchain weight tests to check block winning based on higher account levels.
2019-11-06 09:47:10 +00:00
{ "type": "GENESIS", "recipient": "QjJjjBUJSZAMuYiwTyfJTFthH6SrofjG6d", "amount": "8871800.22712502", "assetId": 1 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "GENESIS", "recipient": "QRh9zNPmz5McxeWx3iCy2xnBRrBoYDZfMJ", "amount": "8739995.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QWGwGBzZG8UeNXJYZq9tjzN6ceriqTgMRd", "amount": "7825760.00000000", "assetId": 1 },
Higher account levels more likely to win blocks Also: RewardShareKeys app now supports only one arg (minter private key) in self-reward-share mode, where recipient public key is derived from minter private key. Added methods to Account for returning 'effective' minting level where minting level for founders is read from blockchain config. (Or returns zero if unable to mint). Changed two Block constructors into static methods that return a new Block as there was way too much work being done to really be called a constructor, especially with all the opportunities to throw an exception too. Main blockchain config updated to reflect near-launch version. Added/changed blockchain weight tests to check block winning based on higher account levels.
2019-11-06 09:47:10 +00:00
{ "type": "GENESIS", "recipient": "QRj4VNEthakckhYpCJMEBhEFk12pa7GPJT", "amount": "7810001.00000000", "assetId": 1 },
Update blockchain.json to nearer launch version
2019-11-12 15:04:41 +00:00
{ "type": "GENESIS", "recipient": "QbdHzyw6q2hMAhg12JFbXSEcbrj43xNnYG", "amount": "7593814.00000000", "assetId": 1 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "GENESIS", "recipient": "QNFWWhmsun3HVUChjck8XqhsQW2tckNxxM", "amount": "7239123.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QeosmemBtE7aosv2QZhq1PTjqpKurKXKzy", "amount": "6185646.80750010", "assetId": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "GENESIS", "recipient": "QU8SzA12SVKPgqpTzRna5itKktGhvEdmgP", "amount": "5931486.64530000", "assetId": 1 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "GENESIS", "recipient": "QNifyiT4LRxtkTp97VgJ23LuZ3qqTgLc33", "amount": "5580161.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QdxuYD638XE84UGdKnb8QPoss1shkMRKYw", "amount": "5389659.68181819", "assetId": 1 },
Update blockchain.json to nearer launch version
2019-11-12 15:04:41 +00:00
{ "type": "GENESIS", "recipient": "QQM9B3ipQcSvATsxb4vgVuYs9kuxgnuBwG", "amount": "5032347.69657146", "assetId": 1 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "GENESIS", "recipient": "QLvdNNMagFRS3B25pAknRH1LMv5urwufHL", "amount": "4996995.00000000", "assetId": 1 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "GENESIS", "recipient": "QLu6X6CVhr6tovNR6k9pQijxN4DHiuLeJS", "amount": "4918400.00000000", "assetId": 1 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "GENESIS", "recipient": "QZgmtZrVPHd1rbHaRjF7zbYdnnS8a8mVZ3", "amount": "4418544.42625000", "assetId": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "GENESIS", "recipient": "QQ44LmLWzkWWe2UJfdvsySkd4ZRs1is3sX", "amount": "4384750.69674618", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QNK7x1kgiA45Zvc5jZFaoDeDzrBrxivwYd", "amount": "4135907.02294526", "assetId": 1 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "GENESIS", "recipient": "QPdkHcN8DBLuxaFf4Q4zXNn3rq2G78VgNt", "amount": "4128493.31116798", "assetId": 1 },
Higher account levels more likely to win blocks Also: RewardShareKeys app now supports only one arg (minter private key) in self-reward-share mode, where recipient public key is derived from minter private key. Added methods to Account for returning 'effective' minting level where minting level for founders is read from blockchain config. (Or returns zero if unable to mint). Changed two Block constructors into static methods that return a new Block as there was way too much work being done to really be called a constructor, especially with all the opportunities to throw an exception too. Main blockchain config updated to reflect near-launch version. Added/changed blockchain weight tests to check block winning based on higher account levels.
2019-11-06 09:47:10 +00:00
{ "type": "GENESIS", "recipient": "QMNdPz11XubtvxXLGeiG3PHKaQW67LkZMp", "amount": "4056950.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QhUWSWWFt6vDy2qNFn68JPTPLjyDrzrh4D", "amount": "3220564.00000000", "assetId": 1 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "GENESIS", "recipient": "QQ7wKkXyQtkwrgG6zeSHNrnDhXQ6fGUsYS", "amount": "3088411.29750001", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QcxXT317FQi3mq9hrQggw7xZujPX63XCq7", "amount": "2779141.00000000", "assetId": 1 },
Update blockchain.json to nearer launch version
2019-11-12 15:04:41 +00:00
{ "type": "GENESIS", "recipient": "QMTcDA7v1dbRXHkryn4ppiM9Q7LGZFNkVT", "amount": "2752011.00000000", "assetId": 1 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "GENESIS", "recipient": "QTekAqCoXPy5R7NE78GXxjSaXBuekZge88", "amount": "2740816.93000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QVQErjTVBkPTphbyDhPvhHKGX2etNXZsgy", "amount": "1999999.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QNPfWoyuvYaScXuCdiCM2PEzvD7PWybBvh", "amount": "1749402.00000000", "assetId": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "GENESIS", "recipient": "QaGhALQm9h3G6m728ZM9L2rrE7Y63nk9e8", "amount": "1637480.00000000", "assetId": 1 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "GENESIS", "recipient": "QV96D15Y3qM1r55odiDf7j2TTYY8jCMJPs", "amount": "1572208.70562500", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QLsEy8syg8EXttzajE8AWGg3CxccNR6YML", "amount": "1300001.00000000", "assetId": 1 },
Update blockchain.json to nearer launch version
2019-11-12 15:04:41 +00:00
{ "type": "GENESIS", "recipient": "QLeNqYjzid2oJFL2iVtcHeAkyunuTsHae4", "amount": "1185185.44326193", "assetId": 1 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "GENESIS", "recipient": "QaUhQiyBZpZWSmFo56zRu2XXfZVL4D2xii", "amount": "1033451.00000000", "assetId": 1 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "GENESIS", "recipient": "QQYnwDmw6Kar4HzoSEG1m2p83mqnY3div7", "amount": "997720.00000000", "assetId": 1 },
Higher account levels more likely to win blocks Also: RewardShareKeys app now supports only one arg (minter private key) in self-reward-share mode, where recipient public key is derived from minter private key. Added methods to Account for returning 'effective' minting level where minting level for founders is read from blockchain config. (Or returns zero if unable to mint). Changed two Block constructors into static methods that return a new Block as there was way too much work being done to really be called a constructor, especially with all the opportunities to throw an exception too. Main blockchain config updated to reflect near-launch version. Added/changed blockchain weight tests to check block winning based on higher account levels.
2019-11-06 09:47:10 +00:00
{ "type": "GENESIS", "recipient": "QMrECKgkohx6ZXEMdLzikqBmAkdyHeQDqL", "amount": "997498.00000000", "assetId": 1 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "GENESIS", "recipient": "QR1GoYcR3iasGNWtJjeNcZFPf9BH4TjCeC", "amount": "858153.00000000", "assetId": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "GENESIS", "recipient": "QNsdyTKN7MVsTYqSyZNPatzRTgNyWDqPZW", "amount": "832163.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QMK8v74dCqJ3d3p4JMZZknvQ1wEJovHEjd", "amount": "805444.62885757", "assetId": 1 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "GENESIS", "recipient": "QMFysMKXLubP21BCYeYiSNP3v5mLhp81Cd", "amount": "676881.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QMdfkckSTcCMKnRRve51SEfZQPVLZg9S7b", "amount": "333086.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QN2UFyKfUsJBHmM5hZrrD2wrwZ1SctSfwQ", "amount": "296438.00000000", "assetId": 1 },
Updated pre-launch blockchain config. Smaller splash graphic.
2019-12-23 15:09:45 +00:00
{ "type": "GENESIS", "recipient": "QMrSxECG64fp2JaoXkw9DYEp6jFPYmh5Jr", "amount": "124684.50000000", "assetId": 1 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "GENESIS", "recipient": "QQRUVwMGifreiLv3FuPTTcA1WbsvhH7Mux", "amount": "102825.00000000", "assetId": 1 },
Higher account levels more likely to win blocks Also: RewardShareKeys app now supports only one arg (minter private key) in self-reward-share mode, where recipient public key is derived from minter private key. Added methods to Account for returning 'effective' minting level where minting level for founders is read from blockchain config. (Or returns zero if unable to mint). Changed two Block constructors into static methods that return a new Block as there was way too much work being done to really be called a constructor, especially with all the opportunities to throw an exception too. Main blockchain config updated to reflect near-launch version. Added/changed blockchain weight tests to check block winning based on higher account levels.
2019-11-06 09:47:10 +00:00
{ "type": "GENESIS", "recipient": "QMQAG28pyv2aZVjWbKoRn39Ytir6rLPnTK", "amount": "100745.00000000", "assetId": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "GENESIS", "recipient": "QWY9HkkCvbKJaqWMEkLbbAJcncywJgy31Q", "amount": "100004.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QQDpKmaKa4uz61CSGVD2zSFaQzeRjaQ8FT", "amount": "100002.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QRQvk1PCt7pNm6JSohtEQQdMEu7BrWjmtr", "amount": "100002.00000000", "assetId": 1 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "GENESIS", "recipient": "QTmKWUXtuQ3ihfigtuLSeFddskmSy3fGN5", "amount": "100002.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QV6rVM4Ywh7TzdN1hgSWVrArKxyEUMuMfs", "amount": "100002.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QTBjfXU6ctuRFBTGkcJySZLqB3L9BdxNbb", "amount": "100002.00000000", "assetId": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "GENESIS", "recipient": "QVdEoLEamBDg8MC8uoMe6fsWrpbd9J3mTL", "amount": "100001.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QW7o4Cd6tvFLe2WryK4eNmFCxz7a9Bs5pJ", "amount": "100001.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QWCEJXDjfZLUfgCJ5V6Uy16KkdigLqEvvo", "amount": "100001.00000000", "assetId": 1 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "GENESIS", "recipient": "QWCTesfyodV4CnKF5cP1RCnksEonZhyJEj", "amount": "100001.00000000", "assetId": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "GENESIS", "recipient": "QVjAVUkKjFHX9N2UQntuPWqHe3PGdBgKgx", "amount": "100000.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QVEuVYqdLfkAyTU5paKkSj2kGid5X7upPi", "amount": "100000.00000000", "assetId": 1 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "GENESIS", "recipient": "QV1FfiEGhYRfNSN5HeXL6ZB1t2NeQJ761N", "amount": "100000.00000000", "assetId": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "GENESIS", "recipient": "QUqDXJzwKrte2YNpR4b44ttKWwnSk6pRTZ", "amount": "100000.00000000", "assetId": 1 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "GENESIS", "recipient": "QQEBW8LU48cuV4uiwQUJ94k3UkJo5eszeg", "amount": "100000.00000000", "assetId": 1 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "GENESIS", "recipient": "QgkNZyrj4zAEAwCDZHTLQ7RcbcCTwcNzPL", "amount": "99999.09400001", "assetId": 1 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "GENESIS", "recipient": "QLecTtNrkgGFAwsSPVpJLgkqdjmjLmsT3F", "amount": "99999.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QVuKDbWVeM92yEta1fagk79NGQsLkvKdCf", "amount": "99999.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QW1NHhKUUPGg2WwMxNyV8VbzmEJJfBTXvy", "amount": "99999.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QUVkDZ2ercosZrRBnC8YZt7et9sXfwfKP4", "amount": "99999.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QQginD86frBSnoNjHEk7JE4zaBWbTqnHk6", "amount": "99999.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QPNuGywKCewuy66DXj7GAJrev5HkcVWjuu", "amount": "99999.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QR2cz8ErrLtcos58iKrQA9aPa8T8kaGc5w", "amount": "99999.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QM1KcVDtpkfsrSyDx6v9okdigbXrNTDKmZ", "amount": "99999.00000000", "assetId": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "GENESIS", "recipient": "QVvq5dE352hhujmDcoj6CaEajp7mBuAuKK", "amount": "99999.00000000", "assetId": 1 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "GENESIS", "recipient": "QWHinsRV49Nf2ue2ZBumK8jWHWrSFhHr91", "amount": "99999.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QSYyv5yJBhkrGeB33NV3NbRYTys9mfkzze", "amount": "99999.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QMHjTaHRi1zTRgXq1vddRiuMBxZpHEJFeb", "amount": "99999.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QVxFXg9QMJp7FFD4XPU2BXR4hySCB9u9Zm", "amount": "99999.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QQa6YP9ocmaMBZPEAPnY7dDekdqo9os4gr", "amount": "99999.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QRdmMSmXk65qRYD8r1yzMBSKFdZf89nmZ8", "amount": "99999.00000000", "assetId": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "GENESIS", "recipient": "QLm1JSR6mph8vXrJ4ZHj5PjchAP7UoN9zm", "amount": "99999.00000000", "assetId": 1 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "GENESIS", "recipient": "QPSEbEbncD9aUrSzNie658DuoFgex641Sd", "amount": "99999.00000000", "assetId": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "GENESIS", "recipient": "QU54p4EUyEr6EDEK7tmWEgwMBkr5MHNJr9", "amount": "99999.00000000", "assetId": 1 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "GENESIS", "recipient": "QRMbQS8Tz9tEH5Wxg6GcoqJ22NqVEcVLFY", "amount": "99999.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QSu3hoF3n9qjMSBfmEn6bGVKNXpn4SrtiX", "amount": "99999.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QQodoJ4PdvwWbPwLErJsXjxtrW2BDZ52Gd", "amount": "99999.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QLpBVjVAxhygwbvHyGLLnKbyvsZ1jUqaWC", "amount": "99999.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QPbWwDxBK3m1LU7uPv55Rq8bwvqLsSjXiE", "amount": "99999.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QVeQRaWcPUNfT3yPWtm6xmuy1hM4N6b1yg", "amount": "99999.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QU6Ac4sVimeehkuK8XcbpFUBVatZ2qgd47", "amount": "99999.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QSCdg6rRRm4jb3r4XNKVytyQAgiTxkAjTw", "amount": "99999.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QQMFd2LfNJCyH6jkQkrK7mdKpjWiJhhFty", "amount": "99999.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QRSeGbHVKqhbUGNzF33DhoJQiPpf9WxZWR", "amount": "99999.00000000", "assetId": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "GENESIS", "recipient": "QQ5jfYBm2tPH4xCdfWDccnzUxhNPHL3VS3", "amount": "99999.00000000", "assetId": 1 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "GENESIS", "recipient": "QW4jfDfsVWHLeLLvdapCG23q5MGajh8mKr", "amount": "99999.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QQAiKxdyRuKT7vPTQGbTitiN4E1WVnWZFa", "amount": "99999.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QTrMWWXU6WyuBRW3WU6duNXpe7AbNog4kP", "amount": "99999.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QQszEg4sqt2o5oN4pdyjxrAwGD3TY5QNfZ", "amount": "99999.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QQsuUfQg57meYToLCx7GTH2DYfAfe4KgQx", "amount": "99999.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QMAsEHJcNAk6Vkzik2bEV6nJ7JZjWAksvi", "amount": "99999.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QP9tgb3pN6FzU3UCmHGW95s9Fmgubzm8md", "amount": "99999.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QMdEATyg41BFbWuMZx829uzBZ8fqYDDERw", "amount": "99999.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QVKtHgZutURJdqnMCRRewsi2WsFNmYGoEE", "amount": "99999.00000000", "assetId": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "GENESIS", "recipient": "QVfFNmHCgWFHhUwLBNBYp32JjL2uusyfsW", "amount": "99999.00000000", "assetId": 1 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "GENESIS", "recipient": "QMMsPuLhww36VQAphKyo29BfhHLeekf8ST", "amount": "99999.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QTAth8ahCmt7ZchLA2N6S5jbF5wCMzyC8H", "amount": "99999.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QLzhvyT3LHzE9DqFrSwNivKMzkB6T1g2DD", "amount": "99999.00000000", "assetId": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "GENESIS", "recipient": "QVfru93ZBLd5XR9YzRBbFHCuYiNV1hJhEw", "amount": "99999.00000000", "assetId": 1 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "GENESIS", "recipient": "QNG1SXqh2uJ4FAy2yxEzUXbRh9Z5KsTvq5", "amount": "99999.00000000", "assetId": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "GENESIS", "recipient": "QRMpfSZ3gcX4gZKCXHam36qpaCC49F2cEt", "amount": "99999.00000000", "assetId": 1 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "GENESIS", "recipient": "QSqcH6aiqnGnP8iGG1cRxMSqtypsqgWprm", "amount": "99999.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QPJbzQTJ7T8fRFu5NbGu9goLZyeLq5Kg3i", "amount": "99999.00000000", "assetId": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "GENESIS", "recipient": "QVXchvzB4PaaXSwhyZcayiTTSe5cje3DE8", "amount": "99999.00000000", "assetId": 1 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "GENESIS", "recipient": "QMTN4ALHmKeJkbVFQQyceEAideDTb1eXdq", "amount": "99999.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QWR8npVGu3w75p5WtgxMikcnujVHEuPBxL", "amount": "99999.00000000", "assetId": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "GENESIS", "recipient": "QRPAESx3b4pWw9C4Q6YLdNYUcCQsWbzEfE", "amount": "99999.00000000", "assetId": 1 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "GENESIS", "recipient": "QRWVqUTDFQRRAKiWjkFCk5pdE1iDw2Cz8s", "amount": "99999.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QMrodSbGSU3zsJVi8BN5X5gPE2xvXGt1ja", "amount": "99999.00000000", "assetId": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "GENESIS", "recipient": "QNLsfHsFcS5xc7BR1fD6aNSZLPt8CEKLuG", "amount": "99999.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QM66cjqmF3WCbbiac6tVU1pLupv2AvU4ev", "amount": "99999.00000000", "assetId": 1 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "GENESIS", "recipient": "QRPnVABwiqT3qBqC6bscfWU6R79RjhUfp9", "amount": "99999.00000000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "QR3mxAS6xdwsRGQXiMVngYmL953gdKcaoa", "amount": "99999.00000000", "assetId": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "GENESIS", "recipient": "QTHLtnDuCz85Xa2jkPuZKhdvyXh8yZH6NJ", "amount": "99999.00000000", "assetId": 1 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "GENESIS", "recipient": "QWA1V7vrRLuhibXjRCSG54y4mkTLf3a4T7", "amount": "99999.00000000", "assetId": 1 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "GENESIS", "recipient": "QLnyXdhGDVEBmByTtjTZihVE3UnReghNyd", "amount": "78296.75000000", "assetId": 1 },
Pre-launch blockchain config / genesis block Also included: auto-update approval script for use by dev-group admins (won't work for anyone else)
2020-03-03 15:58:08 +00:00
{ "type": "GENESIS", "recipient": "QUcPy91Rx5kgbzrZCbR1BgbCLEZx2u3Tqc", "amount": "49996.00000000", "assetId": 1 },
Blockchain replacement for launch. These changes are for allowing devices to be shipped with an interim blockchain config & genesis block, running with "main-net" settings, prior to launch. At launch, an "auto-update" will be broadcast to replace blockchain config & genesis block with the final, launch version. When updated nodes restart (immediately after auto-update) they should notice their existing genesis blocks are invalid and hence wipe their blockchains, effectively starting the final, launch blockchain. To this end, genesis block signatures have been changed to better incorporate values that are likely to change at launch, e.g. block timestamp and transaction data. Added Crypto.dupDigest(), which is effectively Bytes.concat(digest(msg), digest(msg)). No need for HSQLDB repository to backup, or wipe, non-existent files for "in-memory" databases! New interim blockchain config/genesis block. **NOTE** These changes are being committed but require testing. However the auto-update suite requires a pushed commit in order to build an update file!
2019-12-17 16:19:35 +00:00
{ "type": "GENESIS", "recipient": "QTHQ9pFMoraWTCS1tuFzuwWSXu7uVJ18VF", "amount": "40395.00000000", "assetId": 1 },
Updated pre-launch blockchain config. Smaller splash graphic.
2019-12-23 15:09:45 +00:00
{ "type": "GENESIS", "recipient": "QfNkfy7kZ2gwue4Vsoz3YfARwSCS13cwXN", "amount": "14997.00000000", "assetId": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "GENESIS", "recipient": "QN9QJxXAT2ceDwgXvSvjkndeUGXW84xfhQ", "amount": "8505.00000000", "assetId": 1 },
Update blockchain.json to nearer launch version
2019-11-12 15:04:41 +00:00
{ "type": "GENESIS", "recipient": "QVZAQrQHPD8rePZ5hWKx4uj7Ty4GEBe15D", "amount": "2989.50000000", "assetId": 1 },
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
{ "type": "GENESIS", "recipient": "QPZTxWtCmH6Y6zwwntjnPDfKG6zNKRivqJ", "amount": "1282.61375000", "assetId": 1 },
{ "type": "GENESIS", "recipient": "Qgwuvmkqf1wTAxqyFpvUswDqgzWrC6towa", "amount": "0.66600000", "assetId": 1 }
ProxyForging->RewardShare massive refactor & more... 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!
2019-10-29 17:46:55 +00:00
]
Blockchain config (ncluding genesis block) moved out into config file
2018-12-17 13:28:37 +00:00
}
Massive refactor to change 'qora' references to 'qortal'. Blockchain configs will need "v2Timestamp" feature trigger renaming to "qortalTimestamp"! Due to Controller.VERSION_PREFIX changing, peer-to-peer protocol version detection has been changed. Was previous a substring match, now we test peers's buildTimestamp is at least Peer.V2_PROTOCOL_TIMESTAMP_THRESHOLD. Changes in Peer.java. Also added comment and throw() to QortalATAPI.getNextTransactionTimestamp() as this needs given the change to Qortal's block timestamps from legacy Qora. Changes to HSQLDB data types, e.g. QoraAddress to QortalAddress, means existing database will need to be thrown away after this commit!
2020-02-04 12:11:37 +00:00
}
Copy Permalink