[ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - PROOF OF STAKE - ZEROCOIN

[jakiman]

seems like the latest wallet release is broken again somehow.
My Wallet crashed and now its stuck after restart.
Forked again ?

This Shit really needs a testnet.

One older Version even corrupted my wallet before.
So make sure you have a nice n clean wallet.dat backup before you update guys.

Once it crashes (for whatever reason), there is a very high chance your blockchain got corrupt. (or was already corrupt and hence why it crashed)
Have you checked your debug.log after the crash? I highly doubt it has anything to do with the fork unless you are running a really old wallet.

[NotMyFarm]

Just confirming that I'm not having issues with both my Windows & Linux wallets and masternodes on 2.1.2.3.

Same here on Mac version + Staking + Masternodes
no probs at all

[berron]

What wallet version were you using?

DarkNet Core version v2.1.2.3-cb528cd (64-bit)

I think about block 298830 I forked and during more than one hour my wallet saw no new blocks was not able to mint a block neither. In that moment, first forked block was minted and I started to have a new minted block every few minutes, seconds, till I discover the issue. I erased everything except wallet.conf and masternode.conf and things were back to normal. Now I have the wallet working normally, minting and receiving MN payments at the expected frequency.
Salute

[Lariondos]

I'm having hell of a time trying to get my MN's to stay in ENABLED status.

It seems as if even one instance out of the five locks up on my VPS, then all 5 MN's go into MISSING status.

On 8 of my 22 VPS's, between 1 to 4 instances of the darknetd constantly lock up on me. I have to delete the blockchian files, stop the instances, then restart them again, only to have it happen all over again.

When I run the getinfo command on the locked up instances, it says something like "Error loading block database", and occasionally "Cannot connect to server".

Anyone guess why this keeps happening? I'm using mxnsch's script, btw, which automatically uses the latest version of darknetd. My control wallet is also on the latest version. I'm on the $5 VULTR VPS's.

My experience from running some MNs tells me one important thing: Always be sure to have enough RAM. Swap Memory is not a solution if it's backed by HDDs. You will get a much higher CPU load and darknetd reacts badly on this shortage by corrupting the database or simply not catching up with the blockchain and locking up.
So get yourself a VPS with enough base RAM. There are lot's of VPS providers with equal or even lower prices which provide enough ressorces for this task. About 200-250MB per darknetd instance should be enough ATM.

[.cryptic.]

Transaction too large - Cannot create transaction

Always get this error when I try to send coins from my wallet.
Any help is appreciated.

[DRPD]

Transaction too large - Cannot create transaction

Always get this error when I try to send coins from my wallet.
Any help is appreciated.

read this:
https://bitcointalk.org/index.php?topic=1262920.msg16034048#msg16034048

use coin control for a workaround ....

would be very helpful if a dev can tell us the current transaction size limit for dnet.

[.cryptic.]

Transaction too large - Cannot create transaction

Always get this error when I try to send coins from my wallet.
Any help is appreciated.

read this:
https://bitcointalk.org/index.php?topic=1262920.msg16034048#msg16034048

use coin control for a workaround ....

would be very helpful if a dev can tell us the current transaction size limit for dnet.

I selected everything using coin control, still cant even move <1000 coins.
Will try again tonight

[StakeBox]

Transaction too large - Cannot create transaction

Always get this error when I try to send coins from my wallet.
Any help is appreciated.

read this:
https://bitcointalk.org/index.php?topic=1262920.msg16034048#msg16034048

use coin control for a workaround ....

would be very helpful if a dev can tell us the current transaction size limit for dnet.

I selected everything using coin control, still cant even move <1000 coins.
Will try again tonight

Yeah, it is a pain in the ass, I admit. When using coin control you can see the current size of the transaction as you add inputs. The max size right now is 100,000 bytes. It is a good idea to occasionally combine your inputs to keep your wallet slimmed down and to allow for larger transactions when you need them. I was thinking in a future release I would bump that a bit to more accurately reflect the size of of some transactions. That would work, but is kind of a bandaid. With 1MB block size 100KB only allows for 10 max size transactions per block. A better fix would probably be some kind of auto-combine function. I am open to suggestions on how you guys would like to see this dealt with.

[jakiman]

Yeah, it is a pain in the ass, I admit. When using coin control you can see the current size of the transaction as you add inputs. The max size right now is 100,000 bytes. It is a good idea to occasionally combine your inputs to keep your wallet slimmed down and to allow for larger transactions when you need them. I was thinking in a future release I would bump that a bit to more accurately reflect the size of of some transactions. That would work, but is kind of a bandaid. With 1MB block size 100KB only allows for 10 max size transactions per block. A better fix would probably be some kind of auto-combine function. I am open to suggestions on how you guys would like to see this dealt with.

Auto-consolidate would be good as I know that other PoS coins have such feature and works very well. (e.g. https://github.com/bitstar/bitstar)
I have no idea how they do it but I know they do it as dust transactions was a big problem while staking before they implemented that feature.

[4x13]

Transaction too large - Cannot create transaction

Always get this error when I try to send coins from my wallet.
Any help is appreciated.

the issue occurs when you select too many small inputs. try combining the inputs into smaller amounts, then when they are are larger, you can combine them all. This happens with many wallets. It's on the list to be fix'd or at least adjusted to a more manageable size.

[borris123]

do you think people realize that investing in dnet mns is more profitable than btc mining? and thats at current rate as well. quite easily double in value with some small releases. yet alone the truly anonymous transactions. is their a white paper being written for this as well as some more information so we can get an idea of where this coins going?

[mxnsch]

Transaction too large - Cannot create transaction

Always get this error when I try to send coins from my wallet.
Any help is appreciated.

read this:
https://bitcointalk.org/index.php?topic=1262920.msg16034048#msg16034048

use coin control for a workaround ....

would be very helpful if a dev can tell us the current transaction size limit for dnet.

I selected everything using coin control, still cant even move <1000 coins.
Will try again tonight

Yeah, it is a pain in the ass, I admit. When using coin control you can see the current size of the transaction as you add inputs. The max size right now is 100,000 bytes. It is a good idea to occasionally combine your inputs to keep your wallet slimmed down and to allow for larger transactions when you need them. I was thinking in a future release I would bump that a bit to more accurately reflect the size of of some transactions. That would work, but is kind of a bandaid. With 1MB block size 100KB only allows for 10 max size transactions per block. A better fix would probably be some kind of auto-combine function. I am open to suggestions on how you guys would like to see this dealt with.

There is a quite easy solution to this:
1) Generate a couple of new addresses to consolidate to
2) Change to the "Send" Tab
3) Select all inputs in coin control with one click
4) Add additional Receipients (the previously generated ones) with the "Add Recipients" Button on the bottom left
5) Send, ignore the transaction size marker  

If you added enough Recipents, it will work in one run. Be careful that you don't list the same address twice, or you will get an error message.

You will get a single transaction sending everything you request. Of course, a large transaction with lots of outputs will incur a higher fee. It should still be less than sending all transactions separately, however.

[6436346346]

https://www.cryptopia.co.nz/Exchange/?market=DNET_BTC
https://www.cryptopia.co.nz/Exchange/?market=DNET_LTC
https://www.cryptopia.co.nz/Exchange/?market=DNET_XMR

[mikegi]

https://www.cryptopia.co.nz/Exchange/?market=DNET_BTC
https://www.cryptopia.co.nz/Exchange/?market=DNET_LTC
https://www.cryptopia.co.nz/Exchange/?market=DNET_XMR

Nice to see more markets! Also DNET-DOGE, DNET-DOT, DNET-FTC and DNET-UNO.

Currently, only some very optimistic orders  DNET_BTC but it will change.

[berron]

What wallet version were you using?

DarkNet Core version v2.1.2.3-cb528cd (64-bit)

I think about block 298830 I forked and during more than one hour my wallet saw no new blocks was not able to mint a block neither. In that moment, first forked block was minted and I started to have a new minted block every few minutes, seconds, till I discover the issue. I erased everything except wallet.conf and masternode.conf and things were back to normal. Now I have the wallet working normally, minting and receiving MN payments at the expected frequency.
Salute

After analysing my "fork" a bit more, thing start to seem more interesting. Look at this image:



When my wallet started to stack like crazy two of the transactions were accepted. Very strange

Salute

[mxnsch]

Saw that effect yesterday, too. I was not able to replicate today.

[.cryptic.]

My stakes are consistently conflicting from this morning - (around 12hrs back)

[borris123]

masternodes almost touching 1000 again.

[4x13]

Here is next months proposal, please vote..

Proposal for Jakiman to do public Awareness.

"mnbudget vote-many e6f08039a8990fa5e3da404496317da6ff6fc2c984a63167d3b5592556d8e435 yes" to vote in favor

"mnbudget vote-many e6f08039a8990fa5e3da404496317da6ff6fc2c984a63167d3b5592556d8e435 no" to vote against

"mnbudget getinfo public-awareness” to check the status


Let him know if you have ideas etc.

[4x13]

My stakes are consistently conflicting from this morning - (around 12hrs back)

you should zap your tx's use #1, I also had a glitch like this and we are looking into it.