Isn't one of the main reasons of staking to ensure there are always a sufficient amount of peers online? Are there any other benefits to a stake pool other then not needing to run a full node and keep your wallet unlocked. For e.g. will it have a better chance of winning or anything like that. Are there any issues that could arrise from a stake pool having to many people. For e.g. force voting a block in or out?
P2P failover sounds awesome. Definitely going to educate myself on this as I was trying to figure out the best way to keep my wallet online 24/7 between using my dedicated server, raspberry pi or cloud server. Thanks for chiming in on this @davecgh!
Definitely not. Staking can't possibly enforce that. An SPV style wallet could easily perform the necessary staking by communicating with other full nodes (dcrd instances) on the network. It's true that the current wallet requires dcrd to be running, but that will not always be the case. Even if the software did try to enforce that, you couldn't stop people from writing utilities and such do it via the peer-2-peer network without needing to run their own local instance anyways. Well first keep in mind that wallet (dcrwallet) != core network (dcrd). In order to stake you need to have dcrwallet online and unlocked 24/7. With that out of the way, you're correct that the only real benefit of the current pool is that it will provide worry-free voting since it provides multi-location redundancy and automatic failure recovery, neither of which your local setup is very likely to have. However, it is entirely possible that a stake pool could implement proportional reward splitting so stakers receive smaller and more consistent payouts, however that would come at the expense of having to trust the pool with the rewards since it would have to receive them in order to split them out (just like with PoW pools). It's certainly possible, but one of the things that all pools should eventually support is allowing each user to select their individual voting preferences. That way, whenever their ticket comes up and the pool votes on their behalf, it will vote according to their preferences. According to the main page on the test stake pool it already has this planned: "Per user voting selection is a feature that will be added shortly."
Few questions re: solo-stake mining: -Is there a way to inquire on a wallet's currently pooled tickets? -Apart from losing voting right (past block 4096), if your ticket is chosen for POS block reward and you don't have your dcrwallet online and unlocked, is POS reward still sent to wallet? -Which address does it default to deposit into, or does dcrwallet control all addresses simultaneously from the common seed? -Lastly, is the flag --ticketaddress to assign voting rights as well as specify address for rewards, or strictly voting to allow access from a hot wallet? Thanks
Block creates 20 tkts per block so there should be max 2605*20 (block height*20)=5210 No, for receiving reward u must vote for block . And your wallet must me online for voting and receiving reward. Reward will be send to address which purchased a tkt. it only gives voting rights to hotwallet . Reward will be send to address which purchsed a tkt
Thank you for your help, I meant tickets purchased by local wallet but found the command --wallet gettickets Are POS rewards being issued prior to voting @ block 4096? And more importantly as asked above, are currently pooled tickets valid for voting past block 4096 or does the pool re-set when voting begins?
$ dcrctl --wallet help gettickets Code: gettickets includeimmature Returning the hashes of the tickets currently owned by wallet. Arguments: 1. includeimmature (boolean, required) If true include immature tickets in the results. Result: { "hashes": ["value",...], (array of string) Hashes of the tickets owned by the wallet encoded as strings } In other words , use the following command to show all of your tickets: $ dcrctl --wallet gettickets true
Thank you. Just realized no POS rewards issued prior to 4096 in case anyone else is searching. 10% block reward fee for developers is currently being paid out to Dcur2mcGjmENx4DhNqDctW5wJCVyT3Qeqkx along with POW reward in each block. Still curious to know if tickets purchased leading up to block 4096 will be valid once voting begins, or if tickets will be returned.
Hey! I just tried to start stakemining on my VM. But i keep getting these errors: Code: dcrwallet -u xxx -P xxx --walletpass xxx --enablestakemining --balancetomaintain=0 --ticketmaxprice=2 04:54:30 2016-02-20 [INF] WLLT: Opened wallet 04:54:30 2016-02-20 [WRN] DCRW: RPCS: Can't listen on 127.0.0.1:9110: listen tcp4 127.0.0.1:9110: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted. 04:54:30 2016-02-20 [WRN] DCRW: RPCS: Can't listen on [::1]:9110: listen tcp6 [::1]:9110: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted. 04:54:30 2016-02-20 [ERR] DCRW: Unable to create HTTP server: no valid listen address What to do?
Only one usage.....you probably already have another instance of dcrwallet running (on mainnet). Make sure to stop all other instances.
Gotta ask one more question about PoS. I have only like 1 decred on my PoS wallet, but still it doesn't either vote nor stake on any blocks. It just connects them. So my question is do i need to have atleast 2.1 decreds on my balance to start voting/staking? Code: dcrwallet -u xxx -P xxx --walletpass xxx --enablestakemining --balancetomaintain=0 --ticketmaxprice=2 Code: 17:08:07 2016-02-20 [INF] WLLT: Connecting block 000000000000149ee0b18c73bd2f42d3cc3f614412269259a9aa3cb433808d9d, height 3708 17:13:51 2016-02-20 [INF] WLLT: Connecting block 00000000000026805969a7881f09b17f0032475b1d69adbbcdbda1f44d73c02b, height 3709 17:15:26 2016-02-20 [INF] WLLT: Connecting block 0000000000001e7b2e193b078242f7b0f5cc1fcfef89a8f86c24f609c4097b95, height 3710 17:18:45 2016-02-20 [INF] WLLT: Connecting block 0000000000004557fbd7e7d3da2cce4f27e02415d4d254a249069e9bc3dc4f4e, height 3711 17:20:44 2016-02-20 [INF] WLLT: Connecting block 0000000000000b8d416b44b82f50c429d9857dc9e3c41388061657255ac03a48, height 3712
Yes at the present time you need 2 DCR to purchase a ticket. As the PoS difficulty increases over time, tickets prices will too.
dcrctl -u user -P password --wallet purchaseticket "default" spendlimit 2 address purchaseticket command: parameter #2 'spendlimit' must parse to a float64 (code: ErrInvalidType) Usage: purchaseticket "fromaccount" spendlimit (minconf=1 "ticketaddress" "comment") what am i doing wrong?
It needs to be the amount, not the word. i.e ... purchaseticket "default" 2 or if you want to specify a ticket address ... purchaseticket "default" 2 1 Ds....
Speaking about the mainnet version, are there any updates regarding the release of this project? Right now my airdrop coins are just sitting in my web wallet and I'd love to put them to good use. Any information is highly appreciated.