I wouldn't RPC for a Masternodes history.If you find me the RPC calls I have to do on Abe and/or darkcoind, why not.
How do you roll back blocks during a fork in that case?I wouldn't RPC for a Masternodes history.
Do it like I do: create a new table with the Masternode address and a timestamp (and whatever else you want, e.g. amount, pool, ...), and whenever a Masternode gets a payment it is added to that table (or the timestamp gets updated for existing Masternodes).
This way you just have to persist information you already have.
I don't, because for this purpose it's really not needed . The table holds only the latest payment (aka the table is just a snapshot in time), when there's a fork it will automatically be corrected after the fork.How do you roll back blocks during a fork in that case?
Any plans to fix the payout calculator? It still shows roughly half of the actual expected payout. This could influence people's decisions to start a node:
Oh, didn't notice it was wrong. Fixed.Any plans to fix the payout calculator? It still shows roughly half of the actual expected payout. This could influence people's decisions to start a node:
576/2420 x 1.85 (current payout) = .44 DASH per day.
Your site displays .2 DASH per day.
Sweet! Keep up the great work, dude!Added Masternode Detail page
Mainnet URL : https://dashninja.pl/mndetail.html?mnpubkey=
Testnet URL : https://test.dashninja.pl/mndetail.html?mnpubkey=
Add your masternode pubkey at the end of the URL.
Current version: HTML v2.1.0 / JS v2.1.0
(if you see an older version force the refresh by pressing Ctrl+F5)
Check details of your masternode for monitoring info and last expected and actual payments.
Secure Connection Failed An error occurred during a connection to dashninja.pl. The OCSP server has no status for the certificate. (Error code: sec_error_ocsp_unknown_cert)