This one can be a local Multi- Node start wallet. If i remember the first adress with the 1000 vin drk will receive the payment of all within the multi.start wallet. TY again! Byt shouldn't funds go to each wallet instead just first one? I'm not sure but hear from dev that in some case all payments go to the add of first in. I didn't make this conf because too afraid to be hacked and then loose not 1000 drk but all.  Well they go to same wallet but all to first address I use start-many and all my MN addresses get paid separately. There is a conf that payment arrive to one addresse I hear it at the begining of the implementation. I think you make it with import privkey of an already existing MN local. But if you create them from a new wallet with more than one 1K vin, this is happening, (or something like that, well I remember hearing this case because someone detected an address that was receiveing more than other and was explaination of Evan I think or Flare.... ).. Edit UdjinM6... HElpppp this is possible right?? People are often confused by mixing start-many and "send-to-many" (unofficial) features together  start-many - start many MNs by configuring masternode.conf and using start-many command family, no matter how you fund you MNs while you send exactly 1K to MNs addresses send-to-many - fund all your MNs by 1 (one) transaction with many 1K recipients (outputs), for example, send 10k in one transaction to 10 different addresses by 1K each to fund 10 MNs at once. First address in this transaction will receive payments for every another one. However the address you mentioned do not use this feature. It got its payments when coinmine.pl hit a bug we already fixed now. That bug caused pool to pay exact same random lucky MN first few blocks on every restart. However I'd like to thank coinmine.pl for following our updates very quickly and completely complying network rules (while I can't say the same about one another large pool that was already mentioned here...) EDIT: and every other pool who updated too of course, thank you guys! |
|
|
|
Hmm i'm having some trouble with the latest version:
PROCESSMESSAGE: INVALID MESSAGESTART
2015-02-13 23:01:12 Added time data, samples 72, offset +0 (+0 minutes)
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-13 23:01:14 ERROR: CheckProofOfWork() : nBits below minimum work
2015-02-13 23:01:14 ERROR: ReadBlockFromDisk : Errors in block header
Happened two times already, a restart with -reindex works - lets see how long it rolls this time.
Anyone else problems with crashing wallet ?
My disk is ok btw.. Just ran a check ..
Had the same on a couple of nodes, deleted peers.dat and -reindex - all good again! I did -reindex too - did not help, I deleted the blockchain and the peers now.. Lets see In case reindex fails try to sync using bootstrap https://github.com/UdjinM6/darkcoin-bootstrapEDIT: and btw, can I have debug.log please?  udjinm6@darkcoin.io |
|
|
|
Exactly - I'm pulling, not committing.......  Ahhh... I guess I know - Evan rebased few commits not so long ago. So now git tries to fetch and merge it overriding commits in your local repo that you pulled earlier -> making commits to your local repo. So you can reset --hard to somewhere in the past and pull again to fix it. smth like git reset --hard HEAD~100 && git pull In English - take me 100 commits back cleaning everything and then pull latest EDIT: fixed ; -> && |
|
|
|
What's this? From https://github.com/darkcoin/darkcoin
5907263..bdbdbf9 master -> origin/master
* [new tag] v0.11.1.25 -> v0.11.1.25
* [new tag] v0.11.1.24 -> v0.11.1.24
*** Please tell me who you are.
Run
git config --global user.email "you@example.com"
git config --global user.name "Your Name"
to set your account's default identity.
Omit --global to set the identity only in this repository.
fatal: unable to auto-detect email address (got 'rig@rig.(none)')
Anyone? hmm.. it's git message. What's the question exactly? You just need to do what it told you to... I've never had to do this before - hardly anon if I suddenly have to start telling everyone who I am & what I want to download is it? It should ask on commit only actually... |
|
|
|
What's this? From https://github.com/darkcoin/darkcoin
5907263..bdbdbf9 master -> origin/master
* [new tag] v0.11.1.25 -> v0.11.1.25
* [new tag] v0.11.1.24 -> v0.11.1.24
*** Please tell me who you are.
Run
git config --global user.email "you@example.com"
git config --global user.name "Your Name"
to set your account's default identity.
Omit --global to set the identity only in this repository.
fatal: unable to auto-detect email address (got 'rig@rig.(none)')
Anyone? hmm.. it's git message. What's the question exactly? You just need to do what it told you to... |
|
|
|
Hey whats the command to update wallet version to 61000?
-upgradewallet |
|
|
|
There must be something in the air today... I already have 3 new people in my ignore list.  |
|
|
|
Answers please.
Read edit above. Easy test. Sent 1DRK InstantX to an EMPTY walley (ie no other inputs) and immediatly after sent back to original wallet once it IntantX confirmed. Satisfied? Not really… 1) Minotaur26 said 2 mins 2) Do MN's generate diff tokens? YES/NO i.e. if i respend instantx tx's b4 miner confirmations how can double-spending be prevented unless the tokens are diff? educate me You can use them just like any other coins. You can't IX anything that has less then 6 block-level confirmations. https://github.com/darkcoin/darkcoin/blob/master/src/instantx.cpp#L226So MN's are sending I/O valies as yet unconfirmed by mining network? How long does 6 blocks take? Is that a full confirmation? Yep, 6 blocks x ~2.5 minutes per block = ~15 minutes till you can send the same funds using IX. But you can send them as usual or start mixing right after first block. |
|
|
|
Answers please.
Read edit above. Easy test. Sent 1DRK InstantX to an EMPTY walley (ie no other inputs) and immediatly after sent back to original wallet once it IntantX confirmed. Satisfied? Not really… 1) Minotaur26 said 2 mins 2) Do MN's generate diff tokens? YES/NO i.e. if i respend instantx tx's b4 miner confirmations how can double-spending be prevented unless the tokens are diff? educate me You can use them just like any other coins. You can't IX anything that has less then 6 block-level confirmations. https://github.com/darkcoin/darkcoin/blob/master/src/instantx.cpp#L226 |
|
|
|
I'm not German but hey, Google translate does its job! Interesting read for sure! |
|
|
|
i think the .10 (currently 20+ cent) instantx fee is too high and the normal .001 (or .01) transaction fee should apply to anything under 50-100 darkcoins. for anything over 50-100 darkcoins .10 seems reasonable.
the only reason for it to be that high would be because of attacks but i don't think that's the case.
correct me if i'm wrong but don't the masternodes do all the instantx work while the miners do what they always do?
what am i missing?
p.s. please don't quote the trolls because i report them to mods and they deleted the last two spam post from this guy, if people quote him it does no good though.
https://github.com/darkcoin/darkcoin/blob/v0.11.1.x/src/wallet.cpp#L1923-L1927 } else if(useIX && nFeeRet < CENT && nChange > (CENT-nFeeRet)) {
// IX has a minimum fee of 0.01 DRK
nChange -= CENT-nFeeRet;
nFeeRet = CENT;
}
thanks, thats great! so the fee is only around 2 cents? on testnet it's .10 which is around 20 cents right now. http://imageshack.com/a/img912/9637/HqT4X8.jpg0.1 is maximum DS overpay fee, not IX fee - you need to eliminate dead change to save anonymity. Try sending IX only (no DS) transaction and see the difference |
|
|
|
i think the .10 (currently 20+ cent) instantx fee is too high and the normal .001 (or .01) transaction fee should apply to anything under 50-100 darkcoins. for anything over 50-100 darkcoins .10 seems reasonable.
the only reason for it to be that high would be because of attacks but i don't think that's the case.
correct me if i'm wrong but don't the masternodes do all the instantx work while the miners do what they always do?
what am i missing?
p.s. please don't quote the trolls because i report them to mods and they deleted the last two spam post from this guy, if people quote him it does no good though.
https://github.com/darkcoin/darkcoin/blob/v0.11.1.x/src/wallet.cpp#L1923-L1927 } else if(useIX && nFeeRet < CENT && nChange > (CENT-nFeeRet)) {
// IX has a minimum fee of 0.01 DRK
nChange -= CENT-nFeeRet;
nFeeRet = CENT;
}
|
|
|
|
Even if there is 0 MN for a moment, then what? End of the world? We all die? All my drk will dissapear mysteriously?
Drk will exist without, you will not be able to use darksend and instantx ( maybe more feature coming in the future).
You still can send coin received coin ... Sit down take a splif and wait the re-population of MN, i can told you that it will be quick.
*You will not be able to use Darksend mixing but you still will be able to make anonymous transactions using Darksend and already mixed funds (DS balance). |
|
|
|
Guys, I have several reports from different users that wallet crashes sometimes in incomprehensible manner, stops syncing with strange wallet.dat DB error and so on.
After solving this issues with them privately I'd like to ask everyone now:
Please verify your wallet version reported by getinfo is the most recent one.
That's how you do this:
Open "Tools" -> "Debug console" and type "getinfo". Look for the field "walletversion" and if it doesn't match 61000 please do upgrade your wallet buy running it once with -upgradewallet command-line option. Do not forget to close your wallet first and make sure you have the most recent backup available just in case.
Oh never knew about this.. All my MN wallets were still showing "walletversion" : 60000, using the -upgradewallet parameter in the wallet-shortcut fixed it for me: "walletversion" : 61000. Why isn't the wallet upgraded automatically? And what are the risks of running an 'outdated' wallet? And is it perhaps smart to always start the wallet with the -upgradewallet parameter? Guys, I have several reports from different users that wallet crashes sometimes in incomprehensible manner, stops syncing with strange wallet.dat DB error and so on.
After solving this issues with them privately I'd like to ask everyone now:
Please verify your wallet version reported by getinfo is the most recent one.
That's how you do this:
Open "Tools" -> "Debug console" and type "getinfo". Look for the field "walletversion" and if it doesn't match 61000 please do upgrade your wallet buy running it once with -upgradewallet command-line option. Do not forget to close your wallet first and make sure you have the most recent backup available just in case.
Mine said version 60001 until I used -upgradewallet. That is weird! Newly installed QT executable downloaded only a few days ago... "walletversion" is for internal structure of wallet.dat and has nothing to do with qt/daemon executables. Basically Darkcoin started as a litecoin 0.8 fork and wallet.dat structure changed few times already as we had few major versions following changes in bitcoin. The latest structure changes were introduced in Core I believe. They are meant to be compatible however (wallet should give an alert when you have an incompatible version, there are few checks in code). It looks like smth was changed in bitcoin that might break stuff with old versions which considered to be compatible. And btw, there is no need to run with -upgradewallet option every single time but yeah, it might be a good thing to notify everyone next time it changes. |
|
|
|
|
Guys, I have several reports from different users that wallet crashes sometimes in incomprehensible manner, stops syncing with strange wallet.dat DB error and so on.
After solving this issues with them privately I'd like to ask everyone now:
Please verify your wallet version reported by getinfo is the most recent one.
That's how you do this:
Open "Tools" -> "Debug console" and type "getinfo". Look for the field "walletversion" and if it doesn't match 61000 please do upgrade your wallet buy running it once with -upgradewallet command-line option. Do not forget to close your wallet first and make sure you have the most recent backup available just in case.
|
|
|
|
Hello,what is last working wallet? im not sync. ver. 11.0.14 win7 ,pls help!
Yes, 0.11.0.14 is the latest one Try one by one: - remove peers.dat - remove peers.dat and run with -reindex - use bootstrap https://github.com/UdjinM6/darkcoin-bootstrap |
|
|
|
Okay some weird stuff is going on here.. I just updated to 11.0.14 and suddenly my MN wallet is showing more coins than it actually has. http://explorer.darkcoin.fr/address/XvJPvhhtn9AQeL8t6KWCN6bR8UjyRetstaBalance: 1005.95679 DRK Last payment: 23-01-2015 Screenshot shows the same last payment, but the amount of DRK is more..??  And on a sidenote: I haven't received a payment to any of my Masternodes for the past 5 days. I'm either doing something terribly wrong, or am I just unlucky? It sure looks like change... check coin control for a different change address. Has nothing to do with the update. Finally, enforcement is back on so payments should even back out again. Yep, your change is in this address http://explorer.darkcoin.fr/address/Xjs2oimzYocbBbVnE9zsjzx1NfotEspty1 from when you scrapped your payments off your masternode back to 1k. So what does this mean exactly? Everything is fine?  How come the funds on that address show up in my MN wallet? These are the only addresses that my MN wallet has: https://i.imgur.com/G7kC16l.jpg, the one you linked to is a completely different address. Wut... This is your tx http://explorer.darkcoin.fr/tx/27c4183a9c30c3afd26dcb0bcc30b4cfdc640eff65d6231a0e0c21ab1899f2c8#o1 when you moved 69 DRK of MN payments to another address. However "Total in: 69.24965" and "Fee: 0.0007" so you got 0.24895 as change. Go to Preferences -> Wallet -> tick "Enable coin control features". Now go to Send tab and click "Inputs..." (optional - click "List mode") - there should be your MN (1000 DRK), 3 new payments (2.45609, 1.7507, 1.75) and change (0.24895). Try selecting few (let's say 2.45609 and 1.7507) and click ok. You should see a lot of info on Send tab now. Enter some amount less then Amount shown in Coin control section (let's say 1 DRK) and you'll see Change calculated there. Change addresses are generated automatically each time you send coins (if change is >0) to return leftover back to you wallet. You can override it however by using "Custom change address" field. |
|
|
|
|
Show Posts
