Topic: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 3293. (Read 9723782 times)

Seriously?

It is cryptsy not craptsy.

Probably the same person that dumped the ~20k last evening.

20k buy order on craptsy

Sounds Twitter PR Initiative worthy!

https://twitter.com/taoofsatoshi/status/548507346788679680

Enjoy those payments...

Which is completely fine for ramp up.

Every time you receive funds in your wallet you get an output of the transaction into your wallet. You can see your outputs in coin control in your wallet (in the send tab, I believe you have to activate it in settings because it is turned off by default... I can't check now). Sometimes you'll have several outputs in the same address because it was used for several payments you received. When you send a payment the wallet selects one or several outputs and takes the funds from there. You can do this manually if you use coin control. They become the inputs of the new transaction. If the amount is not exact, you'll get a new output with the change when you send that payment. The unspent outputs are those you still have in your wallet. You can check your unspent outputs in coin control, or in the console with the command 'listunspent', or in the blockchain explorer.

For example, check this transaction:
http://explorer.darkcoin.io/tx/1480d81fb88b8e0d2754feca70e2f0a4a905eedd757498bc1a3101a27d68fa76#o0

You can see that output with index 0 has already been spent and you check the transaction in which it was spent (in which it is the input):
http://explorer.darkcoin.io/tx/81c9818d336f7dfb4fc11fa10344207f5477313901ea70fccbaf6628c4f72967#i0

Output with index 1 is still unspent ('Not yet redeemed')... at least for now.

Edit - forgot to add why this is relevant for masternodes
When you send funds from your mastenode wallet you can't use the 1000 DRK unspent output or the masternode will stop working. Let's say you have unspent outputs of 1000, 1, 1, 1, 1.5, 1 and 2.5. If you want to send 5 DRK to someone, you need to use coin control to be sure that you use some of the smaller unspent outputs as inputs in the transaction, not the big one. If you used the 1000 DRK one, you would get back a 995 DRK output as change. The balance in the wallet would be higher than 1000 DRK, but you would not have a working masternode.

Alas, only 2.5% increments from now on.

I literally just got my first 35% payment

hellooooo 35% MN payments (started roughly two hours ago)

https://drk.mn/blocks.html

Lucky you toky Happy for that!

Total Masternodes: 1647 = 1646 actives + 1 inactives (Last refresh: Fri Dec 26 2014 14:34:35)
Estimated daily payout for an active node (blocks with MN payments last 24h: 100%): 0.57 DRK/day (Last Refreshed: Fri Dec 26 2014 14:34:34)

ok. Thanks again for the very informative replies.

I think I'll go and google a few cryptocurrency terms such as "unspent output". I imagine this to be something that's not an explicit representation of the wallet address but that contains the wallet address implicitly or something like that, so it is the equivalent of checking that the wallet has the 1000 DRK.

Trouble is I haven't got enough understanding of basic crypto technical concepts - like signing and stuff. I imagine signing to be something like taking a transaction and then MD5 hashing it or something. Where can I read up on all this basic stuff ?

Many thanks again for the tips. 2 more masternodes coming online when I'm done ! A consequence of 'buying the dip' when DRK was down at 0.003. (Well one of them is anyway).

Time for a small article about WePayDRK, which can be found here.

Not quite correct - it looks for an unspent output of exactly 1000DRK. It actually informs not only the remote masternode itself but also sends message to the whole network that there is a new masternode now. But yes, this won't even happen if remote daemon isn't running yet because before sending that message local wallet checks if port is open on remote one or not.

almost that, see above (unspent output and not an address or an account)

No, it just picks the first one it can found. To run multiple masternodes you have to split you funds to multiple wallets or to use start-many command.

Thanks - that's a very helpful explanation.

So basically:

[1] - set up the remote daemon darkcoind and configure a masternode key

[2] - configure the same masternode key in the local wallet home/library/application support/darkcoin/darkcoin.conf

[3] - send 1000 DRK to any of the addresses in the local wallet

[4] - call "masternode start" and the local wallet arbitrarily chooses an address with >1000 DRK and informs the remote daemon of that address (won't this bit fail if the remote daemon isn't already running ?)

[5] - the remote daemon caches the address and checks at every action that there's still 1000 DRK in the account it's associated with (as do all the other masternodes that have anything to do with it)

Is that it ?

What happens if I now move another 1000 DRK into a different address in the same local wallet and reconfigure the darkcoin.conf (local) for a new masternode and then call "masternode start". Can I repeat the process for a second masternode and masternode start will automatically pick the account that isn't already associated with the first masternode ?

How does that work ?

I do agree, lets first concentrate on fully 100% funcionating anonymation after that InstantX once done these two we can start next feature.

If we want wide adoption, we have to equal the access to the coin for everyone.. by a person, not by a money invested. What if we change the algo to CPU only again without pools, or to Smartphone mining only or at least something like SpreadX11?

told ya price would drop  
this bot is making strange moves today

im watching the price for months ....
these high vol downspikes would be sensless if the bot would not plan to go even lower (50 k dumped   )
i ll buy at wait for 0,004X

Maybe, but I would not know where to start In my opinion, we should focus on perfecting our features first, and then we can think of other uses for the network.

I've had cancelled orders not returned to my balances with Cryptsy before and it normally resolves itself before I raise a support ticket.

I wouldn't be concerned.  I do believe that Cryptsy needs to have an internal review of the problems it has had over the last year.  Its way too unstable for my liking and they won't keep the volume forever if they continue to have problems like this.