Code:
you have to add it twice, one for pending and one for confirmed blocks.
Topic: [VOT] Temp Pool Status (Read 1433 times)
if you want direct links to the block explorer of voitecoin you might whant to add this to the stats html:
you have to add it twice, one for pending and one for confirmed blocks.
you have to add it twice, one for pending and one for confirmed blocks.
Props to OP for being classy. If you'll post your VOT address, I'll donate. Not a lot b/c I'm small timer, but I'd send you 4 VOT, which was half my take from the pool.
In a sorta related topic, I'm trying to setup equihash-solomining (looks like it's a minimalist version of znomp). I've got it and node.js installed (though my first run crash/errors indicate I may need to revisit installation), but I'm confused by some of the configuration instructions.
I think it might be simplest for me to use the p2p option instead of blocknotifier (b/c not really sure where to put the blocknotify=node stuff, maybe votecoin.conf in .votecoin?), but I'm not even sure what port is p2p. I'm guessing 8233 from zcash, but after googling other zcash forks, I've found several different ones. And if I figure that out, in the config.json should the p2p: host and port be the same as the daemons host and port, or should latter be rpcport? Does host 127.0.0.1 work if everything is on the same machine? All input is appreciated.
Tried the "blocknotify" thing. Didn't work. It's indeed part of the votecoind config and should be pointing at port 127.0.0.1:17117 (listener cannot be changed) of z-nomp.In a sorta related topic, I'm trying to setup equihash-solomining (looks like it's a minimalist version of znomp). I've got it and node.js installed (though my first run crash/errors indicate I may need to revisit installation), but I'm confused by some of the configuration instructions.
I think it might be simplest for me to use the p2p option instead of blocknotifier (b/c not really sure where to put the blocknotify=node stuff, maybe votecoin.conf in .votecoin?), but I'm not even sure what port is p2p. I'm guessing 8233 from zcash, but after googling other zcash forks, I've found several different ones. And if I figure that out, in the config.json should the p2p: host and port be the same as the daemons host and port, or should latter be rpcport? Does host 127.0.0.1 work if everything is on the same machine? All input is appreciated.
It gave me a '32512' error in the votecoind debug log. Running it from cmd-line it looked like a PUSH function (wallet to z-nomp) to for skipping to the next block. I think this function was replaced by a RPC GET function (from z-nomp to wallet-RPC).
Props to OP for being classy. If you'll post your VOT address, I'll donate. Not a lot b/c I'm small timer, but I'd send you 4 VOT, which was half my take from the pool.
In a sorta related topic, I'm trying to setup equihash-solomining (looks like it's a minimalist version of znomp). I've got it and node.js installed (though my first run crash/errors indicate I may need to revisit installation), but I'm confused by some of the configuration instructions.
I think it might be simplest for me to use the p2p option instead of blocknotifier (b/c not really sure where to put the blocknotify=node stuff, maybe votecoin.conf in .votecoin?), but I'm not even sure what port is p2p. I'm guessing 8233 from zcash, but after googling other zcash forks, I've found several different ones. And if I figure that out, in the config.json should the p2p: host and port be the same as the daemons host and port, or should latter be rpcport? Does host 127.0.0.1 work if everything is on the same machine? All input is appreciated.
In a sorta related topic, I'm trying to setup equihash-solomining (looks like it's a minimalist version of znomp). I've got it and node.js installed (though my first run crash/errors indicate I may need to revisit installation), but I'm confused by some of the configuration instructions.
I think it might be simplest for me to use the p2p option instead of blocknotifier (b/c not really sure where to put the blocknotify=node stuff, maybe votecoin.conf in .votecoin?), but I'm not even sure what port is p2p. I'm guessing 8233 from zcash, but after googling other zcash forks, I've found several different ones. And if I figure that out, in the config.json should the p2p: host and port be the same as the daemons host and port, or should latter be rpcport? Does host 127.0.0.1 work if everything is on the same machine? All input is appreciated.
Cheers
its ok about the donation part ... no worries at all I setup equihash-soloming when it first came out , but since znomp was out, i switched to it and use it just for solo mining ...
for the blocknotifier , i actually never changed the default setup and never activated this alternative script for it ... didn't have much time to look into how it works!
if you use 127.0.0.1 , then i think only connections from that machine will work, usually i just leave the "redis server" ip at 127.0.0.1 ... all other ip's i give them my local ip 192.168.xxx.xxx (also never used 0.0.0.0)
p2p ... also is another thing i never looked into or had much time to investigate ... again ... i only setup the pools to learn , and personally mine on them with my 3 GPUs that i have so far
))don't hesitate to ask anything , and apologies in advance if i dont get back right away ... i usually check in here once or twice a day
found it on line 298 (actually changed it to shield 125 instead of 100):
A block is usually bigger than 125 VOT, due to collected fees, it may be 125.002 or so. So you will end up with another shielding for those 0.002 in second run. I would suggest you to put there different value, like 200 or even 1000.
Props to OP for being classy. If you'll post your VOT address, I'll donate. Not a lot b/c I'm small timer, but I'd send you 4 VOT, which was half my take from the pool.
In a sorta related topic, I'm trying to setup equihash-solomining (looks like it's a minimalist version of znomp). I've got it and node.js installed (though my first run crash/errors indicate I may need to revisit installation), but I'm confused by some of the configuration instructions.
I think it might be simplest for me to use the p2p option instead of blocknotifier (b/c not really sure where to put the blocknotify=node stuff, maybe votecoin.conf in .votecoin?), but I'm not even sure what port is p2p. I'm guessing 8233 from zcash, but after googling other zcash forks, I've found several different ones. And if I figure that out, in the config.json should the p2p: host and port be the same as the daemons host and port, or should latter be rpcport? Does host 127.0.0.1 work if everything is on the same machine? All input is appreciated.
In a sorta related topic, I'm trying to setup equihash-solomining (looks like it's a minimalist version of znomp). I've got it and node.js installed (though my first run crash/errors indicate I may need to revisit installation), but I'm confused by some of the configuration instructions.
I think it might be simplest for me to use the p2p option instead of blocknotifier (b/c not really sure where to put the blocknotify=node stuff, maybe votecoin.conf in .votecoin?), but I'm not even sure what port is p2p. I'm guessing 8233 from zcash, but after googling other zcash forks, I've found several different ones. And if I figure that out, in the config.json should the p2p: host and port be the same as the daemons host and port, or should latter be rpcport? Does host 127.0.0.1 work if everything is on the same machine? All input is appreciated.
Hello everybody who is interested in running own pool for VoteCoin. If you plan to use z-nomp, beware that you need to make some manual adjustments to make it work.
First of all, you must ensure you are using latest VoteCoin sources to build the coin daemon, due to fixed RPC reporting for block reward.
Then, the main problem with performance is that VoteCoin, similarly like zcash and others, need to send the coinbase (newly mined) coins to a shileded address first, this takes a lot of CPU time, and then wait 10 blocks, and then transfer from shileded to unshielded T address, which takes another minutes of CPU power and another 10 confirmations, before it can be paid out to miners. This basically means you need a powerful machine to process payments, in ideal case 8 CPU cores and 8GB of RAM or even more, else it will be delayed and the delay will increase over time.
There is one more problem, z-nomp has hardcoded limit to unshield only 100 ZEC at a time. This causes problems with insufficient balance if your pool has lots of hashrate, since mined blocks are 125 VOT but unshielding gets you only 100 so it needs to run TWO unsielding operations in order to unshield 125. You should modify the file z-nomp/libs/paymentProcessor.js, search for "unshield no more than 100 ZEC at a time" and fix it there, remove the if(amount>100) amount=100; part.
First of all, you must ensure you are using latest VoteCoin sources to build the coin daemon, due to fixed RPC reporting for block reward.
Then, the main problem with performance is that VoteCoin, similarly like zcash and others, need to send the coinbase (newly mined) coins to a shileded address first, this takes a lot of CPU time, and then wait 10 blocks, and then transfer from shileded to unshielded T address, which takes another minutes of CPU power and another 10 confirmations, before it can be paid out to miners. This basically means you need a powerful machine to process payments, in ideal case 8 CPU cores and 8GB of RAM or even more, else it will be delayed and the delay will increase over time.
There is one more problem, z-nomp has hardcoded limit to unshield only 100 ZEC at a time. This causes problems with insufficient balance if your pool has lots of hashrate, since mined blocks are 125 VOT but unshielding gets you only 100 so it needs to run TWO unsielding operations in order to unshield 125. You should modify the file z-nomp/libs/paymentProcessor.js, search for "unshield no more than 100 ZEC at a time" and fix it there, remove the if(amount>100) amount=100; part.
nice one with the 100 VOT shielding ... didn't know that one .... nice
)Update:
found it on line 298 (actually changed it to shield 125 instead of 100):
Code:
// unshield no more than 100 ZEC at a time
if (amount > 125.0)
amount = 125.0;
if (amount > 125.0)
amount = 125.0;
Hello everybody who is interested in running own pool for VoteCoin. If you plan to use z-nomp, beware that you need to make some manual adjustments to make it work.
First of all, you must ensure you are using latest VoteCoin sources to build the coin daemon, due to fixed RPC reporting for block reward.
Then, the main problem with performance is that VoteCoin, similarly like zcash and others, need to send the coinbase (newly mined) coins to a shileded address first, this takes a lot of CPU time, and then wait 10 blocks, and then transfer from shileded to unshielded T address, which takes another minutes of CPU power and another 10 confirmations, before it can be paid out to miners. This basically means you need a powerful machine to process payments, in ideal case 8 CPU cores and 8GB of RAM or even more, else it will be delayed and the delay will increase over time.
There is one more problem, z-nomp has hardcoded limit to unshield only 100 ZEC at a time. This causes problems with insufficient balance if your pool has lots of hashrate, since mined blocks are 125 VOT but unshielding gets you only 100 so it needs to run TWO unsielding operations in order to unshield 125. You should modify the file z-nomp/libs/paymentProcessor.js, search for "unshield no more than 100 ZEC at a time" and fix it there, remove the if(amount>100) amount=100; part.
First of all, you must ensure you are using latest VoteCoin sources to build the coin daemon, due to fixed RPC reporting for block reward.
Then, the main problem with performance is that VoteCoin, similarly like zcash and others, need to send the coinbase (newly mined) coins to a shileded address first, this takes a lot of CPU time, and then wait 10 blocks, and then transfer from shileded to unshielded T address, which takes another minutes of CPU power and another 10 confirmations, before it can be paid out to miners. This basically means you need a powerful machine to process payments, in ideal case 8 CPU cores and 8GB of RAM or even more, else it will be delayed and the delay will increase over time.
There is one more problem, z-nomp has hardcoded limit to unshield only 100 ZEC at a time. This causes problems with insufficient balance if your pool has lots of hashrate, since mined blocks are 125 VOT but unshielding gets you only 100 so it needs to run TWO unsielding operations in order to unshield 125. You should modify the file z-nomp/libs/paymentProcessor.js, search for "unshield no more than 100 ZEC at a time" and fix it there, remove the if(amount>100) amount=100; part.
if you want to remove this pie chart from the stats page you can comment that part in "website/pages/stats.html"
you just add the "" to that section to comment it out
Code:
you just add the "" to that section to comment it out
Have it working now thx for your hints!
Thinking about setting this up on one of my hosts.
Any more adjusted you did after your first experience?
Thinking about setting this up on one of my hosts.
Any more adjusted you did after your first experience?
not really ... this should work ok for you ... there are some adjustments done to the coin's config file .... "~/.votecoin/votecoin.conf" .. just add the following line to give more room for rpc calls:
Code:
rpcworkqueue=128
and also adjust some settings in the pool's config files increase the "blockRefreshInterval":
- in the config.json
Code:
"defaultPoolConfigs": {
"blockRefreshInterval": 60,
"blockRefreshInterval": 60,
- and in the pool_confis/votecoin.json :
Code:
...
"walletInterval": 10,
....
"paymentProcessing": {
....
"paymentInterval": 600,
"walletInterval": 10,
....
"paymentProcessing": {
....
"paymentInterval": 600,
and that should stop the rpc errors that might show up in znomp daemon ... they won't stop the running of the pool , but obviously the default rpc queue values somehow flood the rpc and need to be increased!
Have it working now thx for your hints!
Thinking about setting this up on one of my hosts.
Any more adjusted you did after your first experience?
Thinking about setting this up on one of my hosts.
Any more adjusted you did after your first experience?
Yes that helps a lot!
Thank you very much.
I will definetly try this later.
Thank you very much.
I will definetly try this later.
note that you need to generate at least 3 t-addresses:
- two go in the "votecoin.json" in the pool_configs , for shielding & processing payments
- third you use to mine (use in your miner as address to mine to)
and of course the z-addr to shield the new coins from the mined blocks (this also goes in the "votecoin.json" in the pool_configs)
Code:
"address": "t-addr-1",
"zAddress": "z-addr",
"tAddress": "t-addr-2",
"zAddress": "z-addr",
"tAddress": "t-addr-2",
and 3rd t-addr for your miner usage ....
Yes that helps a lot!
Thank you very much.
I will definetly try this later.
Thank you very much.
I will definetly try this later.
Thx for your effort to get it sorted out.
For me: t1gJTLWuXL5caoo5ZFYY7zTFkjbEiuQt9V4
i allready got some coins partially ... so i believe the other part will come as well.
Thx again and hoping to see this coin rise some day
btw. i tried to setup a pool on my own but i am not sure how to setup the json file as their is no example for votecoin.
Any pointers?
For me: t1gJTLWuXL5caoo5ZFYY7zTFkjbEiuQt9V4
i allready got some coins partially ... so i believe the other part will come as well.
Thx again and hoping to see this coin rise some day
btw. i tried to setup a pool on my own but i am not sure how to setup the json file as their is no example for votecoin.
Any pointers?
which json file? the coin's in znomp? if so, this is what i did:
- in "pool_configs" i added the following
Code:
nano votecoin.json
and then copied & modified the config from other coins ... this is my actual votecoin.json
Code:
{
"enabled":true,
"coin": "votecoin.json",
"address": "t1h7Dut3kXTDaPUhqM4v3mm7rbreL7FE5ry",
"zAddress": "zcBBhYdasCiBpkimmTZcCjH7df5aVCz7oNQoPv5We65MKwcg6Djy8mfr39Mh9eedvFBMnZ3dW6QRLLqmXBHartjtmGJTc6G",
"tAddress": "t1cdge5th3DtrixsCtwZxUH79xB443hok1o",
"walletInterval": 20,
"rewardRecipients": {
},
"tlsOptions": {
"enabled": false,
"serverKey":"",
"serverCert":"",
"ca":""
},
"paymentProcessing": {
"minConf": 10,
"enabled": true,
"paymentMode": "prop",
"paymentInterval": 300,
"minimumPayment": 0.1,
"maxBlocksPerPayment": 3,
"daemon": {
"host": "127.0.0.1",
"port": 19833,
"user": "myRPCuser",
"password": "myRPCpass"
}
},
"ports": {
"19834": {
"tls":false,
"diff": 0.05,
"varDiff": {
"minDiff": 0.04,
"maxDiff": 16,
"targetTime": 15,
"retargetTime": 60,
"variancePercent": 30
}
}
},
"daemons": [
{
"host": "127.0.0.1",
"port": 19833,
"user": "myRPCuser",
"password": "myRPCpass"
}
],
"p2p": {
"enabled": false,
"host": "127.0.0.1",
"port": 19333,
"disableTransactions": true
},
"mposMode": {
"enabled": false,
"host": "127.0.0.1",
"port": 3306,
"user": "me",
"password": "mypass",
"database": "kmd",
"checkPassword": true,
"autoCreateWorker": false
}
}
"enabled":true,
"coin": "votecoin.json",
"address": "t1h7Dut3kXTDaPUhqM4v3mm7rbreL7FE5ry",
"zAddress": "zcBBhYdasCiBpkimmTZcCjH7df5aVCz7oNQoPv5We65MKwcg6Djy8mfr39Mh9eedvFBMnZ3dW6QRLLqmXBHartjtmGJTc6G",
"tAddress": "t1cdge5th3DtrixsCtwZxUH79xB443hok1o",
"walletInterval": 20,
"rewardRecipients": {
},
"tlsOptions": {
"enabled": false,
"serverKey":"",
"serverCert":"",
"ca":""
},
"paymentProcessing": {
"minConf": 10,
"enabled": true,
"paymentMode": "prop",
"paymentInterval": 300,
"minimumPayment": 0.1,
"maxBlocksPerPayment": 3,
"daemon": {
"host": "127.0.0.1",
"port": 19833,
"user": "myRPCuser",
"password": "myRPCpass"
}
},
"ports": {
"19834": {
"tls":false,
"diff": 0.05,
"varDiff": {
"minDiff": 0.04,
"maxDiff": 16,
"targetTime": 15,
"retargetTime": 60,
"variancePercent": 30
}
}
},
"daemons": [
{
"host": "127.0.0.1",
"port": 19833,
"user": "myRPCuser",
"password": "myRPCpass"
}
],
"p2p": {
"enabled": false,
"host": "127.0.0.1",
"port": 19333,
"disableTransactions": true
},
"mposMode": {
"enabled": false,
"host": "127.0.0.1",
"port": 3306,
"user": "me",
"password": "mypass",
"database": "kmd",
"checkPassword": true,
"autoCreateWorker": false
}
}
and in the coins folder i just copied the zdash.json and renamed it to votecoin.json and edited as follows:
Code:
{
"name": "votecoin",
"symbol": "vot",
"algorithm": "equihash",
"requireShielding": true,
"txfee": 0.0004
}
"name": "votecoin",
"symbol": "vot",
"algorithm": "equihash",
"requireShielding": true,
"txfee": 0.0004
}
hope this helps
Thx for your effort to get it sorted out.
For me: t1gJTLWuXL5caoo5ZFYY7zTFkjbEiuQt9V4
i allready got some coins partially ... so i believe the other part will come as well.
Thx again and hoping to see this coin rise some day
btw. i tried to setup a pool on my own but i am not sure how to setup the json file as their is no example for votecoin.
Any pointers?
For me: t1gJTLWuXL5caoo5ZFYY7zTFkjbEiuQt9V4
i allready got some coins partially ... so i believe the other part will come as well.
Thx again and hoping to see this coin rise some day
btw. i tried to setup a pool on my own but i am not sure how to setup the json file as their is no example for votecoin.
Any pointers?
There are always wrinkles in new stuff and you did advertise it as a test, so I'm sure everyone will be patient.
FWIW, I mined some solo blocks yesterday via the daemon and they were both 125 VOT. Also that smallest earning address in QYyY is at 7.49 but on the site it shows immature balance of 8.16. So maybe it'll all filter through in time.
Sorry the experiment wasn't more successful for you, sorry it's produced extra work and thanks again for trying to let people mine on a pool.
FWIW, I mined some solo blocks yesterday via the daemon and they were both 125 VOT. Also that smallest earning address in QYyY is at 7.49 but on the site it shows immature balance of 8.16. So maybe it'll all filter through in time.
Sorry the experiment wasn't more successful for you, sorry it's produced extra work and thanks again for trying to let people mine on a pool.
Yes
after I stopped the stratum all the workers disappeared from the website so i only got the balances of the ones that found blocks (because their addresses were still in the found blocks list) but the "t1WpVUgqVjJG8FxSxd18j6KVL8FLBtdQYyY" address didn't find any blocks so i only had its balance from right before i stopped the stratum port !!! ... i updated the list above ... thank you for pointing it out ) There are always wrinkles in new stuff and you did advertise it as a test, so I'm sure everyone will be patient.
FWIW, I mined some solo blocks yesterday via the daemon and they were both 125 VOT. Also that smallest earning address in QYyY is at 7.49 but on the site it shows immature balance of 8.16. So maybe it'll all filter through in time.
Sorry the experiment wasn't more successful for you, sorry it's produced extra work and thanks again for trying to let people mine on a pool.
FWIW, I mined some solo blocks yesterday via the daemon and they were both 125 VOT. Also that smallest earning address in QYyY is at 7.49 but on the site it shows immature balance of 8.16. So maybe it'll all filter through in time.
Sorry the experiment wasn't more successful for you, sorry it's produced extra work and thanks again for trying to let people mine on a pool.
Thank you so much for your understanding
) i actually , because of this , can't mine on my own (as i usually do) until all of this is cleared out of the pool !! but it seems that it will ... don't know how it will after the last git update (correcting the rpc / block reward error) as it seems that pool payment is stuck at block 10536 !!!i think its trying to pay the 100 VOT it originally thought the block was for, but the wallet rpc is giving back some error because i keep seeing this on the pool backend:
Code:
2017-09-14 11:45:29 [Pool] [votecoin] (Thread 3) Could not parse rpc data from daemon instance 0
Request Data: {"method":"getblocksubsidy","params":[],"id":1505382329499}
Reponse Data: Work queue depth exceeded
2017-09-14 11:45:29 [Pool] [votecoin] (Thread 4) Could not parse rpc data from daemon instance 0
Request Data: {"method":"getblocksubsidy","params":[],"id":1505382329506}
Reponse Data: Work queue depth exceeded
2017-09-14 11:45:29 [Pool] [votecoin] (Thread 1) Could not parse rpc data from daemon instance 0
Request Data: {"method":"getblocksubsidy","params":[],"id":1505382329507}
Reponse Data: Work queue depth exceeded
2017-09-14 11:45:29 [Pool] [votecoin] (Thread 2) Could not parse rpc data from daemon instance 0
Request Data: {"method":"getblocksubsidy","params":[],"id":1505382329508}
Reponse Data: Work queue depth exceeded
Request Data: {"method":"getblocksubsidy","params":[],"id":1505382329499}
Reponse Data: Work queue depth exceeded
2017-09-14 11:45:29 [Pool] [votecoin] (Thread 4) Could not parse rpc data from daemon instance 0
Request Data: {"method":"getblocksubsidy","params":[],"id":1505382329506}
Reponse Data: Work queue depth exceeded
2017-09-14 11:45:29 [Pool] [votecoin] (Thread 1) Could not parse rpc data from daemon instance 0
Request Data: {"method":"getblocksubsidy","params":[],"id":1505382329507}
Reponse Data: Work queue depth exceeded
2017-09-14 11:45:29 [Pool] [votecoin] (Thread 2) Could not parse rpc data from daemon instance 0
Request Data: {"method":"getblocksubsidy","params":[],"id":1505382329508}
Reponse Data: Work queue depth exceeded
i contacted the pool devs on gitter and waiting for their reply to see!!
Do not worry about the lost VOT (100 VOT reward instead of 125). That was caused by error on RPC reply which reported only 100VOT. Those coins are lost forever, there is no way to restore them. In all cases, please update your votecoin software to the latest sources from GITHUB, the issue was fixed.
There are always wrinkles in new stuff and you did advertise it as a test, so I'm sure everyone will be patient.
FWIW, I mined some solo blocks yesterday via the daemon and they were both 125 VOT. Also that smallest earning address in QYyY is at 7.49 but on the site it shows immature balance of 8.16. So maybe it'll all filter through in time.
Sorry the experiment wasn't more successful for you, sorry it's produced extra work and thanks again for trying to let people mine on a pool.
FWIW, I mined some solo blocks yesterday via the daemon and they were both 125 VOT. Also that smallest earning address in QYyY is at 7.49 but on the site it shows immature balance of 8.16. So maybe it'll all filter through in time.
Sorry the experiment wasn't more successful for you, sorry it's produced extra work and thanks again for trying to let people mine on a pool.
actually some coins started to show in the payout address !!! ... so maybe the pool will manage itself and make all the proper payouts after all ... anyways i will be giving it its space for now to see how it will resolve itself for the next few hours (i really have to sleep to get to work tomorrow!!!)
t1cdge5th3DtrixsCtwZxUH79xB443hok1o is supposed to be the pool's payout address, and
t1h7Dut3kXTDaPUhqM4v3mm7rbreL7FE5ry is supposed to be the pool's t-address where the new coins are forged into! (and that's the address that will show up first on the block explorer http://explorer.votecoin.site/ )
Code:
{
"address": "t1cdge5th3DtrixsCtwZxUH79xB443hok1o",
"account": "",
"amount": 99.99960000,
"confirmations": 0,
"txids": [
"bc8cf9ad81bfc29e5519a78043a05f92601b2808770d5c56f3dc000898c24ba8"
]
},
{
"address": "t1h7Dut3kXTDaPUhqM4v3mm7rbreL7FE5ry",
"account": "",
"amount": 99.99980000,
"confirmations": 48,
"txids": [
"c9c8934b93d73ad5be4905919075874830a3a6ae3afd71b0f35db4a590dac9b8"
]
}
"address": "t1cdge5th3DtrixsCtwZxUH79xB443hok1o",
"account": "",
"amount": 99.99960000,
"confirmations": 0,
"txids": [
"bc8cf9ad81bfc29e5519a78043a05f92601b2808770d5c56f3dc000898c24ba8"
]
},
{
"address": "t1h7Dut3kXTDaPUhqM4v3mm7rbreL7FE5ry",
"account": "",
"amount": 99.99980000,
"confirmations": 48,
"txids": [
"c9c8934b93d73ad5be4905919075874830a3a6ae3afd71b0f35db4a590dac9b8"
]
}
t1cdge5th3DtrixsCtwZxUH79xB443hok1o is supposed to be the pool's payout address, and
t1h7Dut3kXTDaPUhqM4v3mm7rbreL7FE5ry is supposed to be the pool's t-address where the new coins are forged into! (and that's the address that will show up first on the block explorer http://explorer.votecoin.site/ )
here are the payouts as per the last shares from the pool:
I will stop the stratum port now so miner won't be able to submit any more work to pool
update
i still have to see what exactly is coming out of these blocks ... so far the pool is stopped at 59 blocks (which should yield 5900 VOT!!!) it seems that i'm missing some 203 VOT from the above list that should belong to someone ... if i can't manage to find out who they belong to, i will just split them equally on the above addresses !!! or maybe donate them to the VOT project!!!
this is what is in the wallets right so far:
and in the z_balance:
obviously so far one block is 100 VOT and with the transfer from initial t-addr to z-addr (for shielding) and back again to t-addr (so it could be spent) this take 0.0002 VOT in tx fees ... so the one block ends up to equal 99.9998 VOT
I will keep updating here until all blocks are completely
| t1KJsHPhmbzfvR44vcUGCPUqo7sYKTAcH6M | 2604.14412608 |
| t1RwCz5gd5iPt7JeqB7DGNBegu2ULE7wRoT | 1183.53563387 |
| t1TPDfbpoh7dRt6zCjK9g3fEKJj8S35qXHF | 883.99578362 |
| t1MKj4wLPXQmzHdftnH83Esee1yHX9ZPEXL | 536.68558575 |
| t1XW9gCyR4LJR2WFtNcpzheFKuLA5fCeYNT | 349.47816575 |
| t1YHSjw9ng3EAESFBF1NtmrJW6JtGvwRAJM | 202.38068641 |
| t1gJTLWuXL5caoo5ZFYY7zTFkjbEiuQt9V4 | 131.59523047 |
| t1WpVUgqVjJG8FxSxd18j6KVL8FLBtdQYyY | 8.16188803 |
| Total | 5697.59641357 |
I will stop the stratum port now so miner won't be able to submit any more work to pool
update
i still have to see what exactly is coming out of these blocks ... so far the pool is stopped at 59 blocks (which should yield 5900 VOT!!!) it seems that i'm missing some 203 VOT from the above list that should belong to someone ... if i can't manage to find out who they belong to, i will just split them equally on the above addresses !!! or maybe donate them to the VOT project!!!
this is what is in the wallets right so far:
Code:
{
"address": "t1h7Dut3kXTDaPUhqM4v3mm7rbreL7FE5ry",
"account": "",
"amount": 99.99980000,
"confirmations": 47,
"txids": [
"c9c8934b93d73ad5be4905919075874830a3a6ae3afd71b0f35db4a590dac9b8"
]
}
"address": "t1h7Dut3kXTDaPUhqM4v3mm7rbreL7FE5ry",
"account": "",
"amount": 99.99980000,
"confirmations": 47,
"txids": [
"c9c8934b93d73ad5be4905919075874830a3a6ae3afd71b0f35db4a590dac9b8"
]
}
and in the z_balance:
Code:
{
"transparent": "0.00",
"private": "599.9996",
"total": "599.9996"
}
"transparent": "0.00",
"private": "599.9996",
"total": "599.9996"
}
obviously so far one block is 100 VOT and with the transfer from initial t-addr to z-addr (for shielding) and back again to t-addr (so it could be spent) this take 0.0002 VOT in tx fees ... so the one block ends up to equal 99.9998 VOT
I will keep updating here until all blocks are completely
Jump to: