My opinion on any price speculation/pump: Darkcoin shouldn't associate with any [community coordinated] pump. The market will turn it in a way it should just like it did for lite: more and more people realize there is no development and no future in ltc - drop like a rock; more and more people aware of fundamental drk features and continuous development - slowly gaining attraction and value. Want some privacy and instant txs? Buy it, use it. Don't need any of these? Well, it's your money anyway... but think twice maybe  PS. btw pumping in public just screams of punishment for doing this - you'll attract sharks and wales and they will have it leaving you with nothing. |
|
|
|
i was thinking about the Darksend mixing which is under review to make it more fluid, faster
and with better feedback towards users .. what if the wallet could give its users a visual signal when
it detects a lot of mixing going on? That way people who need to do some Darksend mixing for themself
will know it will be a good time to join the mixing right then and there.
Think of it like a traffic light, if its on green it means a lot of mixing going on while if its on red there is little
to no mixing going on.
I like this idea - the client can pull the hashespersec from the network, it could pull some kind of mixing stat too and present it on the overview page in realtime, people are suckers for shiny flashing lights. Such data might even be useful to the devs? Client doesn't pull [network] haspersec, it's calculated from diff https://github.com/darkcoin/darkcoin/blob/master/src/rpcmining.cpp#L17However every client is aware of mixing queue so maybe we can use this info in some way actually... |
|
|
|
[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 ?)
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. [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)
almost that, see above (unspent output and not an address or an account) 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 ?
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. |
|
|
|
What is the step in the masternode setup that links a masternode privkey (the one you specify in darkcoin.conf) with the funded wallet address ?
It links together on "masternode start" For example, I'd like to set up 2 masternodes. Can I use the same wallet for them both just by generating a second address and second masternode privkey ?
The only thing I'm not very sure of is how do I know which wallet address applies to which masternode privket that I generate.
Yes, you can do this by using "start-many". However this feature is experimental. More info on current implementation/setup https://github.com/darkcoin/darkcoin/pull/62Can I stop and restart the remote masternode without ever bringing the cold wallet online ?
Not sure what you are asking exactly. In terms of "masternode start" and "masternode stop" - no but you can restart daemon as usual (darkcoind stop) without the need of issuing "masternode start" again. Does the remote masternode always ckeck for the 1000 DRK if I restart it ? How does it know what wallet address to check ?
Yes, it does. Actually everyone check everyone. When MN is started by "masternode start" it sends message that it's now associated with some vin (txid + output number) where 1000 DRK is, some masternodeprivkey and ip address. You can associate it only with your own 1000DRK because you need to sign that message with the corresponding private key. Every message this MN will send then should be signed with that masternodeprivekey. So when some MN is trying to do something anyone can verify is it legit or not (is 1000DRK still there, does signature match and so on). |
|
|
|
hi, anyone know how to run linux darkcoin wallet  i kept getting warning about updating wallet or other node not yet updated EDIT :: using latest wallet darkcoin-0.10.17.24-linux you are most likely still using an old wallet.dat file you need to back up your wallet then start your client with the -upgradewallet command oh yes, im still on old wallet.dat. this kind of info should be on the first page... im confused for few days. thanks EDIT :: i cant remove the warning, i even rename the old wallet.dat and creating new wallet.dat still showing warning.  do i need to change darkcoin.conf or delete the whole .darkcoin folder btw i will wait for few hours and then delete the folder, btw i already dumprpivkey i assume i can import it back after upgrade try removing peers.dat first EDIT: btw, I wouldn't worry too much about it. If you are using the latest version you should be fine anyway. |
|
|
|
..... Better buy some DRK.  Hey, UdjinM6, Don't you think you could spend your time on more valuable place? like coding, creating or enjoy your life leisurely? Roger that! |
|
|
|
First of all - you are in the wrong thread. Second - I wouldn't be that optimistic about these numbers. I read through this briefly: 95+% of changes there are 1) automatic code cleanup made by IDE and 2) a copy-paste of updated bitcoin code. The meaningful part is hard to derive from that mess.  . The majority is anon with ringsig & bloom filters, and Thin mode. Just search keywords "Ringsig", "Bloom", "Thin", ... you may be able to do that, i've seen your post history. Sure DRK updates were easier to read, but it's not that difficult for a coder The only thing right in your sentences, is that it's not the good thread You are wrong. I'm not saying that there is no meaningful code. Read my answer again, I saw all these parts too. However... - Ring Signatures is not an innovation https://en.bitcoin.it/wiki/CryptoNote- https://github.com/bitcoin/bitcoin/blob/master/src/bloom.cpp- "thin mode" is something to verify that node has blocks in history, not sure why you need this at all. not interested. Let's stop this discussion. Better buy some DRK. |
|
|
|
First of all - you are in the wrong thread. Second - I wouldn't be that optimistic about these numbers. I read through this briefly: 95+% of changes there are 1) automatic code cleanup made by IDE and 2) a copy-paste of updated bitcoin code. The meaningful part is hard to derive from that mess. |
|
|
|
Hey guys, Revamped the news section of darkcoin.guide, available here: http://darkcoin.guide/newsPlease let me know what you think. Also, if anyone knows of other news sources, I'll gladly include them. Only quality sources without spam content though. Nice progress there! |
|
|
|
Welcome our new core developer, Vertoe!
Vertoe (AKA “vertoe”) is an acadamic grade software engineer fallen in
love with C/C++. She is working as a freelance programmer for a well
known NGO in the area of netactivism and recently started backporting
upstream features to enable a modern Darkcoin Core reference implementation.https://www.darkcoin.io/about/team-contact/ Really well deserved reward! Congratulations! |
|
|
|
What is your conf file name I got Coin2.1.conf tried other names , but still nothing.
....... For some reason that way it worked for me just fine while it didn't work for me when I didn't specify this... dunno why... ....... Thanks for the help man, im lost on the issue other than giving nodes.. besides have you checked your firewall to make sure the wallet isnt blocked penetrator? must be some glitch on my side... it works now without any params, sorry for confusion)) |
|
|
|
What is your conf file name I got Coin2.1.conf tried other names , but still nothing.
Yes, it should be Coin2.1.conf https://github.com/kalisto2002/Coin2.1/blob/ebec4b57887a8f78cd7cee1c4c97271e0d387395/src/util.cpp#L1121But you can use command line parameters to use the one you need -conf=path/to/your/conf/file For some reason that way it worked for me just fine while it didn't work for me when I didn't specify this... dunno why... Anyway, just paste addnodes there, name it Coin2.1.conf or whatever and add -conf=Coin2.1.conf to your command line (make sure names match) and you should be good. Btw there is no need to specify exact path if it's in default folder and defaults are: https://github.com/kalisto2002/Coin2.1/blob/ebec4b57887a8f78cd7cee1c4c97271e0d387395/src/util.cpp#L1058-L1061I would also recommend to use bootstrap.dat to speed up syncing: - Grab latest file there http://c2chain.info/bootstrap- Extract downloaded file until you get bootstrap.dat - Place bootstrap.dat in default folder - Start qt-wallet and prepare to wait a lot - it should be a much faster then downloading block by block but still will take a while and wallet will not respond all that time. You can verify it's still doing something by checking debug.log in default folder |
|
|
|
It started eating all CPU time and memory on my server not so long ago and I can't find what is the issue yet  so I temporary turned it off to give blockchain explorer some breath... |
|
|
|
Thanks for sharing! He is an awesome speaker! I'm so excited of every his speach.. He can talk about complicated things in such way that 5 year old child can get it. Or even Canadian senators  EDIT: Q&A section there is awesome! |
|
|
|
2014-11-26 21:32:29 1.5009 1006.50265 DRK
Hell yeah!!
Congrats! |
|
|
|
|
Show Posts
