-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Release 3.0.0e https://www.jelurida.com/ardor/downloads sha256 checksums: fedee64db5de70d51b09ae7f7fb7ff0f92e8fa91f1ffd65aa0e32dda574f4662 ardor-client-3.0.0e.zip This is an experimental release for testing only. Source code is not provided. Change log: This is the first release of the Ardor pruning and snapshotting feature. It is experimental and for testnet use only. A new testnet has been created, starting from a snapshot of the current testnet as of Dec 8, 2020. Users having testnet balances as of the snapshot height, block 6248612, should have the same initial balances on this new testnet. The 3.0.0e release cannot be used with the current 2.3.3 mainnet or testnet however. To enable pruning of child chain transactions, the nxt.pruneChildChains=true property must be set (default is false). If this is enabled, child chain transactions are not processed during blockchain download and are pruned from storage during normal operation. During download, only the parent Ardor chain is processed; when the download is finished, the blockchain state (consisting of child chain balances, asset holdings, aliases, etc - everything an account owns) is loaded from a state snapshot, downloaded from the network and confirmed by at least 720 blocks or as set in nxt.stateSnapshotConfirmations. The peer networking port for the 3.0 testnet is 16874 and the API port is 16876 (SSL port 16877, if enabled). The different ports allow this version to be run in parallel with 2.3.3 mainnet or testnet instances. Block times have been set to 30 s for this testnet. Users familiar with running Ardor nodes are invited to join the 3.0 testnet by installing this release and report any issues in our support forum, https://talk.jelurida.com Apart from the major new pruning and snapshotting feature, there should be no difference in functionality compared to 2.3.3. -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEvs/qm2srO/+g27NEDPnHRy2AuLkFAl/qUdIACgkQDPnHRy2A uLkz4Q/+PGDBOT6MlV8ZsLRIkV9vad3n6H8U06MMhDMdZe60jlLYhbXW5ZSY4EmJ CcS9QBN4L28reaBLnfdD1ac569HhpJWesXGfIBTlbn5st+Nha9hZSuhVKBi7MQUt 4XBQN25fdeu5uc5wQF81HdKX18+P+2Kvqjtst1oxpVmOccQqhz84Ego2oiGwM+2Q UJtFTKZX8vIuQvOxEuUzehR6w3VcYwogM1imfrZ/N+TQIx70vNQz+Li2+yL07CGY y/KsnOYQT/kw1O+PYQnhnjQHhSLWnNky2nUgDh6zkhPCGa9+pj2iDRGXSXzGzOL1 ikV0yhVtYo80mtYcCpm1uyjaSJNyTIo9PU1XVmvvWJnz0ZlTXwVoy+W+5zty4n0p mzSBVJ1zzwNeSVrfej51+6N2WmOiATSTlE2uNG3efMUO8Q5ym5gNCWRg8HZv+y8r fzhl4oY/fVzrdPw15uiFIvewS6eVowvzP3Xcn2tEn1x1/WKWIc0MApIhKIVD7P4l ZcyCtM5QSKX7TJrnD7Hwfn1h23Wyc/mGcjpbxVlWBcyBTjdLemK6h7OgzGuftbVA L5wt46eISxPWuWR36fiq9f+QqnU4CVMegk800/a5wdaNNW9n8ArYme2K6sQZmfFW SKx+Zrcb9p/8S9oK3WLyjiE6FpYV1WZwFmyb/fD/dlmEf+z8bdI= =udb2 -----END PGP SIGNATURE-----
A few questions if someone could help or point me in the right direction.
When did the block time change from 1min to 30 sec? I did see someone asking about testing nxt at 10sec. What type of issues would something like that create for Ardor or nxt? How viable is it to push block times towards 1 sec for either? What issues would that create?
Another question, when did the confirmation change to 720 blocks from 1440? Why is 720 enough now? Is there somewhere I can find this info, or possibly an answer.
A further note would be can NFT storage or something be a part of future releases. I know NFT are easy to create, but a specialised NFT folder would be good considering recent appeal. Not sure the best set up for it but i'm sure would make for good pr.
Thank you very much for your time in answering these questions. A long time member of nxt and Ardor.
720+ (seems weird +1440 :))
Block times are 60 seconds for mainnet, 10 seconds for the regular testnet and 30 seconds for this new testnet (3.0.0 with pruning).
About the 720 blocks it's been like that for quite some time. You will probably find the details in the changelog.
Thanks for your response. Have had a look will keep looking. I assume it was at the nxt>>ardor change.