Has anyone seen cheaplin. Such a shame he's not about any more. He has great skills. Would be great to see him again..  Or at least hear from him that we know he is doing all right. I emailed his personal email a few months ago asking if he was OK and didn't get a reply  |
|
|
|
who did they interview ?? They interviewed me, I was surprised to find they didn't mention my name. |
|
|
|
Is enforcement still off?
I used to get MN payments like a clockwork. I understand that now we have 1740 MNs but still the timing of the MN payments doesn't feel right.
Enforcement was off for a bit while I updated the reference node, you should start receiving payments like clockwork again soon. |
|
|
|
Welcome Francis Reynders to the team! Francis has joined the team as a core developer and has an academic degree in Computer science, is Linux LPIC-2 certified and has over 20 years of development experience. For his day job he's currently working as an Integration specialist for ITSM systems. As for contributions, he rewrote the new start-many implementation, keepass integration ( https://github.com/darkcoin/darkcoin/pull/96) and is currently working on reimplementing the dsee/dseep commands for the masternode protocol to make them more efficient. Welcome! https://darkcointalk.org/threads/welcome-francis-reynders-to-the-team.3429/ |
|
|
|
Hi guys. I have a question. I have 3 masternodes, but seems that i have some problem with payments.
Mn 1 get payed 5 times for all december.
Mn 2 was payed 8 times.
Mn 3 was payed 12 times.
I did all the same for 3 of them.
Do you know what is wrong? I think that 12 is normal for 31 days, but 5??
And btw the Mn 3 with 12 payments is partialy unlisted 25 % ,other 2 are active 100 %
Is any of you have experienced same problem?
I've just discovered a bug that was only activated after 1000 masternodes were reached. The result is increased variance between payments the more masternodes we get. It's very simply to fix and I'll patch the reference node right away. It'll take a couple days for it to take effect, then we should have pretty even payments again (like after we launched). |
|
|
|
Hello darkers, I think something really bad happened to me.
Had to move my 1005DRKs from A to B.
It was the first time I opened the wallet on B, so it generated the keys and dled the blockchain as well. I sent 1DRK for testing from A and it arrived to B.
Then I proceeded with the 1005 payment (used the same destionation adress) and it has been stucked @0 confirmation, so I closed and reopened the wallet on B.
The bad thing is that the wallet generated the keys and dled the blockchain again as it was the first time been opened (using the .zip download from darkcoin.io). I didn't make a backup tho, so no way I can the destination address on my wallet again, amirite?
The payment is still @0 confirmations, transaction id is d8fbedf74271cc704b8bc3fadd664a9a98afa02a165d7c878999a4057478e1b8 .
Is there any way to recover this?
Have you tried using -rescan ? It seems like it wasn't broadcasted. or --zapwallettxes |
|
|
|
A MN flare runs for me dropped. He has not replied yet - I guess he's busy - but I am curious. After the node dropped I deleted peers.dat (as he told me to do it last time it dropped), started the wallet again, and tried a masternode start. It gave me: Parse error: unbalanced ' or "I successfully changed the password but the a message after a masternode start this time was: not capable masternode: Unknown.Any idea what that means? Not that I worry, but in the ADD world I occupy, if flare does not respond in five minutes  i start scouring the Net for answers. Than it downed on me, you guys know these thingies so please explain this issue to a poor n00b like myself... Try using these binaries and let me know if it works: https://github.com/darkcoinproject/darkcoin-binaries/tree/4e12da9add6bedebf4f12cff0efe1a6b940df9c3 |
|
|
|
Anyone knows why average spacing between DarkCoin blocks is approximately 157 seconds instead of 150 seconds? I remember that when creating SpreadCoin several months ago I noted that there is a small bug in DarkCoin difficulty retarget which causes block generation to be a bit slower than it should be. But it seems that I lost this knowledge. When I'm now looking at difficulty retarget it looks correct to me, although a bit obfuscated.
This has been known for some time and isn't worth fixing. I'll explain why: https://github.com/darkcoin/darkcoin/blob/master/src/main.cpp#L1607https://github.com/darkcoin/darkcoin/blob/master/src/main.cpp#L1453One of them is computing 24 blocks and one is computing 23. So: 1/24.0 == 0.0416 2.5*1.0416 == 2.604 (minutes) Statistically it's doing exactly what it should! |
|
|
|
The Spreadcoin dev is reviewing the Darkcoin code and just posted this: https://bitcointalk.org/index.php?topic=715435.msg9839488#msg9839488Mr.spread,what's status of masternode and darksend developmnet?
It is far from ready yet but I think I found a potential vulnerability in DarkCoin which allows miners (actually pools) to not pay part of the block reward to masternodes. DarkCoin wallet checks the following things for each new block: 1) There is a payment to master node. 2) There is a payment with the same amount as a payment to master node should be (30%). But there is no check that this is the same payment. This means that if you generate a block you can pay 0.0000001 DRK to masternode and pay 30% and (70% - 0.0000001 DRK) to yourself as separate coinbase outputs. Such blocks should be accepted by DarkCoin network but I haven't tested it on testnet so I can't be 100% sure. I don't want any vulnerabilities out the wild so thought I'd check here. This is what happens when "Enforcement" is off, right? Or is this a separate issue and potential vulnerability? Patched: https://github.com/darkcoin/darkcoin/commit/ee8174a2c690b995003449a046b036d87ae25b5d (sorry, trimmed space after every line) Compiling 10.17.24 now, feel free to update from source |
|
|
|
hi.please help meeeeeeeeeeeeeee.my dark coin to wallet http://darkcoin-e.com/ and all my dark coin not send to any address dark coin.whyyy? ? after 1 months is Processing and not complete yet. and i send email too cantact support and not Response .please help me.i lost all my dark coin what was your darkcoin wallet address there? Wasn't that website outed as a scam? I remember seeing something from tunfa...  can we add the warning to the first post of this tread (?)! please. Added, We should try to get it removed from Google: https://www.google.com/safebrowsing/report_phish/ |
|
|
|
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/
|
|
|
|
|
Is there a Spanish community somewhere? I was just asked and I actually don't know of one.
|
|
|
|
There's no fee besides what you'd pay the miner in a transaction fee. |
|
|
|
Amazing...this is definitely a post instantX feature. Just out of curiosity - what happened to masternode IP obfuscation using the IP unwrapping/layering tech?? Same question here.  Actually, I would love to see a list of upcoming features with the order they will be worked on. In my head that is: 1. Darksend Rewrite/Improvements/Hardening 2. InstantX 3. IP Obfuscation 4. 2 Factor Authorization Evan (other Dev team members), is this correct? Also, more importantly, can a list like this be officially maintained? Dates are not needed, but as a community member just knowing the development plan a few months in the future would be nice. Agreed, I'd rather do the IP tech before 2FA. |
|
|
|
|
Show Posts
