Topic: . - page 54. (Read 491736 times)

Database file link is corrupted. Can you post correct one?

Great!

Great to see it! Thanks.

No, there is no need for a HZng version anymore. :-)

Seems that I forgot to mention that the new release uses the nxt gui.

Is a HZng version also available?

We are happy to announce a new release hz-v4.0e.
You can find the new release on github
https://github.com/NeXTHorizon/hz-source/releases/tag/hz-v4.0e

We provide two versions hz-v4.0e and hz-v4.0e-node.
hz-v4.0e-node is a preconfigured  as a public node. By default it allows access to the  API server for everyone.
Contrary to hz-v4.0e-node, hz-v4.0e is configured to only allow access to the API from localhost.
There are no other differences between this two versions.

Changelog:

This is a experimental release. An upgrade is not mandatory, but recommended.

This is the first release which stores all derived objects in the database,
instead of keeping all of them in memory only.

Derived objects are those that are constructed based on the information already
available in the blockchain blocks and transactions - i.e, Accounts, Aliases,
Assets, Goods, Purchases, Orders, Trades. Storing them in the database instead of
in memory means the Asset Exchange and the Digital Goods Store can scale to much
higher number of assets, orders, and goods, without requiring an ever growing
amount of memory for each node.

Using a standard SQL database tables to store those records also allows for
much more sophisticated queries, and allows third parties to write and execute
custom queries against those tables directly, without being dependent on the NRS
http API only.

By storing the state of all derived objects as of the current height, plus their
state at previous heights up to 1440 blocks back, it is possible to completely
eliminate the need for blockchain rescans on startup, and on fork resolution.

On upgrade from, this version will perform an initial
build of the derived objects tables, which on a fast machine takes about 7 minutes,
but may take longer depending on your hardware. The database size will grow
during this rescan, but after shutdown should shrink back to around 1 GB.

There will be no rescans on subsequent restarts, and the startup time is now
reduced to a few seconds only. There will also be no rescans at runtime on block
pop offs.

Derived object tables are kept small by trimming them, only records needed to
allow rollback of up to 1440 blocks back are kept. If you need to preserve and
query historical information going back all the way to height 0, this trimming
can be disabled by setting nhz.trimDerivedTables=false (default is true) in
nhz.properties. After changing this property, a rebuild of the derived tables
can be triggered using the new scan API request, see below.

The default number of rollback records kept can be increased while still keeping
trimming enabled, by setting nhz.maxRollback to a higher value (default and
lowest possible is 1441). This should provide a compromise for those who want to
keep history of more than the default 1441 blocks, yet want to avoid the
performance penalty of never trimming the derived objects tables.

To allow for the increased use of database, default max number of database
connection has been increased to nhz.maxDbConnections=30, lock timeout
increased to nhz.dbDefaultLockTimeout=60 and MVCC is enabled by default
in nhz-default.properties.

H2 cache size allocation is improved. If nhz.dbCacheKB is not set,
the H2 cache will vary linearly from 16MB for JVM heap size 160MB, to
256MB for heap size 640MB or higher. This should allow low end devices
to run without needing a custom setting for the nhz.dbCacheKB parameter,
and prevent excessive memory use on machines with plenty of memory too.

To prevent overloading a node with invalid peer addresses, the maximum total
number of known peers is limited to nhz.maxNumberOfKnownPeers (default 3000).
Once this number has been reached, new peer addresses are not added, and peers
that have been last connected to more than a week ago are removed from the known
peer list, provided the node has enough connected public peers, until the number
of known peers is again reduced to below nhz.minNumberOfKnownPeers (default
1000).

Enforce that the nhz-default.properties file used matches the version of the
current release.

Updated jetty to version 9.2.10.

UPnP refactored.

DbShell servlet:
A command line access to the H2 database at runtime is now possible at:
http://localhost:7776/dbshell
This page uses the H2 shell tool to allow querying the database at runtime,
directly from the browser, without having to enable auto server mode in the jdbc
url. The debug APIs which allow direct manipulation of the blockchain
database are always enabled, but are protected with a password, which needs
to be set in the nhz.adminPassword property. Password is not required when the
API server is listening on the localhost interface only (the default).
The password protection can be disabled by setting nhz.disableAdminPassword=true
in nhz.properties.

Test servlet:
The usability of the http://localhost:7776/test API access page has been improved.

Enhanced nhz.allowedBotHosts property to also accepts a range of addresses
using CIDR notation.

New API requests:

Monetary System/Currencies (feature not yet enabled):
currencyBuy, currencySell, currencyReserveIncrease, currencyReserveClaim, currencyMint,
getAllCurrencies, getAccountCurrencies, getAccountCurrencyCount, getCurrency, getCurrencies,
getCurrencyFounders, getCurrencyIds, getCurrenciesByIssuer, getCurrencyAccounts,
getCurrencyAccountCount, getExchanges, getExchangesByExchangeRequest, getExchangesByOffer,
getAllExchanges, getCurrencyTransfers, getBuyOffers, getSellOffers, getOffer,
getAccountExchangeRequests, getMintingTarget, issueCurrency, publishExchangeOffer,
transferCurrency, canDeleteCurrency, deleteCurrency, searchCurrencies

Accounts:
getAccountBlockCount, getAccountBlocks, getAccountLessors

Aliases:
getAliasCount, deleteAlias

Asset Exchange:
getAssetAccounts, getAssetAccountCount, getAssetTransfers, getAccountCurrentAskOrders,
getAccountCurrentBidOrders, getAllOpenAskOrders, getAllOpenBidOrders, searchAssets,
dividendPayment (not yet enabled)

Blocks:
getBlocks, getECBlock

DGS (feature not yet enabled):
getDGSGoodsCount, getDGSGoodsPurchases, getDGSGoodsPurchaseCount, getDGSPurchaseCount,
getDGSTags, getDGSTagCount, searchDGSGoods

Util:
longConvert

Debug:
clearUnconfirmedTransactions, fullReset, popOff, scan, luceneReindex

Network:
addPeer, blacklistPeer

getAccountBlocks - like getAccountBlockIds, but returning full block JSON.
If includeTransactions parameter is true, also includes the transaction JSON.

getAccountCurrentAskOrders and getAccountCurrentBidOrders -
like getAccountCurrentAskOrderIds and getAccountCurrentBidOrderIds, but returning
full order JSON.

getAllOpenAskOrders and getAllOpenBidOrders now replace getAllOpenOrders, but
only returning ask or bid orders respectively, and allow firstIndex/lastIndex
pagination.

getAssetTransfers - retrieves the asset transfers for an asset, account, or both,
sorted by height descending.

getAssetAccounts - accepts an asset parameter and returns all accounts holding
this asset as of the current height, and the asset quantity each one owns, sorted
by asset quantity descending.
Takes an optional height parameter to allow retrieving asset holders as of a
previous blockchain height.

getAccountLessors - retrieves the accounts that have leased their balance to the
specified account, takes an optional height parameter to allow querying previous
blockchain heights.

The historical height query feature in getAssetAccounts and getAccountLessors
depends on the specified height records still being available, i.e. either table
trimming disabled, or maxRollback set high enough to cover that height.

longConvert - an utility API to convert between signed long ids as used in the
database and unsigned long ids represented as strings. Accepts an id in either
form and returns both the signed and unsigned versions.

getECBlock - returns the ecBlockId and ecBlockHeight given an optional timestamp,
current time if not supplied.


New debug API requests:

The following requests are used for debugging purposes only and should not
normally be needed. They are protected with a password, which needs
to be set in the nhz.adminPassword property. Do not enable on a public node
where the API is accessible to anyone.

fullReset - delete and redownload the whole blockchain.

popOff - accepts a numBlocks or height parameters, and pops off that many blocks
or back to that height. If table trimming is enabled (default), at most 1440
blocks can be popped off. Derived object tables are rolled back to the specified
height and blocks and transactions after that height are deleted.

scan - accepts a numBlocks or height parameters, rolls back the derived object
tables to that height and rebuilds them by rescanning the existing blockchain
from that height up again. Does not delete blocks or transactions from the
blockchain, unlike the popOff request. A request to rescan more than 1440 blocks
when table trimming is enabled will do a full rescan starting from height 0.
Setting validate parameter to true will also re-verify signatures and re-valudate
blocks and transactions during the rescan.

Added clearUnconfirmedTransactions debug API to force clearing of the
unconfirmed transactions pool.

API changes:
The limit parameter is no longer accepted by the getAskOrderIds, getBidOrderIds,
getAskOrders and getBidOrders APIs, as firstIndex/lastIndex parameters are now
used instead for pagination.

New API calls for peer management: addPeer and blacklistPeer. AddPeer will add
a peer address or IP, optionally with port number, to the list of known peers
and will try to connect to it. BlacklistPeer (password protected) will
blacklist a peer, for the default blacklisting period.

The following existing APIs now allow optional pagination using firstIndex,
lastIndex parameters:

getAccountBlockIds, getAccountCurrentAskOrderIds, getAccountCurrentBidOrderIds,
getAccountTransactionIds, getAccountTransactions, getAliases, getAllAssets,
getAllTrades, getAskOrderIds, getAskOrders, getAssetIds, getAssetsByIssuer,
getBidOrderIds, getBidOrders, getDGSGoods, getDGSPendingPurchases, getDGSPurchases,
getTrades

The limit parameter is no longer accepted by the getAskOrderIds, getBidOrderIds,
getAskOrders and getBidOrders APIs, as firstIndex/lastIndex parameters are now
used instead for pagination.

getAccountBlockIds in addition to allowing pagination now returns the blocks
in descending order, as this is more useful when showing the newest blocks
on top in the client.

getTrades now accepts an optional account parameter, in addition to asset, to
allow retrieving trade history for a specific account, for either all assets or
a specific asset only.

getUnconfirmedTransactions and getUnconfirmedTransactionIds now also accept
the RS account number format.

The Trade JSON now includes buyer and seller account ids, the height at which
the trade occurred, the asset name, and the heights at which the ask and bid
orders were accepted in the blockchain.

The Asset JSON now includes total number of transfers, and number of accounts
holding the asset.

parseTransaction does not just return an error when trying to parse an invalid
transaction bytes or JSON, but adds a validate=false field, plus the actual error
message, in addition to the parsed transaction JSON.

getState no longer includes total effective balance.

Packaging changes:

To prevent intentional misunderstanding of why jar files hashes are never
reproducible, the class files are now left unpacked in a classes subdirectory
after compilation, instead of being packaged in a nhz.jar file. The run.sh and
run.bat scripts have been modified to include this directory on the classpath
instead of the nhz.jar file. Those who still prefer to build a nhz.jar file, can
easily do that with the included jar.sh script, and modify the classpath to use
it. A pre-built nhz.jar file will still be included for a few releases.

Checkpoints updated.

Please see source code for more details.

tl;dr

This is an experimental release. An upgrade is not mandatory, but recommended.

This release is the first release which stores all objects in the h2 database.
On a normal VPS the database upgrade can take up to 2.5 hours.

The fastest way (about 5 minutes, depends on download bandwidth) to upgrade to  
hz-v4.0e is to download the database, instead of upgrading or starting from scratch
with an empty database.

release files: https://github.com/NeXTHorizon/hz-source/releases/tag/hz-v4.0e
database file: http://hz-services.com/downloads/nhz_dbs/ 20150729-nhz_db-4.0e.zip

Fine, I'm curious

Sorry for the wait, it's done now.
The test script worked fine on testnet, fingers crossed for the payout tonight.
I squished the data with zlib but I'm sure that's no problem for you.

Almost 4 weeks later, I would like to ask the question again.

Most likely today evening.

Any update? When 4.0 wallet will be released?

Perfect use of the technology. Great use case for the future...

An Interview with Mayor of London candidate, George Galloway

JR: What are your priorities and major policies that you would enact if elected as Mayor London?

GG: I’ll give you the latest one which is attracting a lot of attention, and that’s the Mayor Chain that I have proposed. I’m going to put the entire £17 billion budget online in real time in block chain and this will allow the public in to see exactly what’s coming in and exactly what’s going out, and where it’s going to, and make representation about it.

http://felixonline.co.uk/politics/5648/an-interview-with-mayor-of-london-candidate-george-galloway/

I am giving away some FREEDOM fo free to community members. This action will help with the distribution with FREEDOM since I don't operate from a web address or have a massive promotional campaign either. I will at some point create a topic involving FREEDOM and have a little feedback from community on this. As a precursor this current action sets the stage as such. 

If you are interested in receiving some of the tokens all you have to do is send a message to me (link to follow) on HZ platform where you describe what freedom means to you, or how do you see yourself involved with freedom. Freedom is very broadly defined so it does not need to be economic freedom as such - whatever you feel like conveying in the message is up to you - you can freely choose, even if it is just some quote that really means a lot to you. If you want to keep the message private then encrypt it, if you want it to be public then leave out the encryption.

After receiving and reading the messages concerning freedom I will send some freedom to your account.

Here is the link to my account. https://explorer.horizonplatform.io/?page=asset&id=1918076501414611727

Here is my account NHZ-KGPH-8FZU-W843-EQPA2

Happy messaging 

Yeah! Altsheets is doing very good work, And he is really a very active member. I really don´t know if he joined how part of team or he is a collaborator of Horizon Team.

WOW!! You've really put in a lot of work!

... to do this post was still on my TODO list ... finally finding the time to react ...

HZ block explorer

For a long time I wanted to link to an official page about my asset - but there was none.
Everyone agreed it would be nice to have one page per asset in the block explorer, but
there was not enough time in the HZ team to build such an extension. I had suggested
"just send me an example page, and I code that for you" - but I did not have a clear concept
what that would mean in the end: Tons of challenges, studying a huge amount of code,
and actually learning a new programming language - this time in 3 hours *lol*.

Trying to code without debugging - impossible. I need a running system. When thankfully,
pharesim opened the sourcecode, I installed it from github, solved all problems, wrote a
manual how to ... and then I let the backend run. Which took more than a day to finish!  
But now I have a working system to code extensions!  -->

HZ B.E.E.f.A = HZ Block Explorer Extension for Assets

All in all ~35 hours of work later, I successfully finished coding & debugging - my first time ever in PHP!

You can read my proud announcement (4 consecutive postings), my happiness about the tips I received,
and -YIEHAH- pharesims announcement, that it got merged into the official version now (github pull request).
My elaborate documentation of the whole endeavour is in this github README.

(Actually, why I was on it anyways, I could also fix an old bug in the block explorer, zero balance when RS.)

You can discuss my suggestion, an "asset warnings" function - in this horizon forum thread.

Now that it is merged, this is how it looks- a dedicated page for each of the 149 assets:
(click for larger)

Thanks for merging my code. I am intrigued that you could already realize my "from the future" idea
showing the "Number of Transfers" (see my sourcecode lines 117-123). I had not expected that it would work
already, because the current HZ API does not tell us the number of transfers. But the B.E. knows more :-)



TL;DR:
My block explorer extension is online! A page like this one exists for all assets now!
Try it out, perhaps by using that page to tell us about your favorite HZ asset?

thx for linkin my website! unfortunately there are a lot of bugs on it and i dont have any free time left.. its really annoying. please dont rely on the info there... hopefully i will have some spare time in the next week to fix some bugs..

2 days left.

3.9.2 announcement on bct was on July 15, 2015, 12:49:26 AM
https://bitcointalksearch.org/topic/m.11882155

Thanks a lot for your quick answer, MaWo.