Topic: [ANN] VGC - VegasCoin - page 5. (Read 74455 times)

Nova is no longer closing. Novaexchange was sold to Goobit of Sweden and should be back in a month or two. Many coins could be delisted though.

Does this coin trade on any exchanges?  We can not find any stable exchanges for it.

Nova is closing.

?

No exchanges means the coin is dead pretty much.

https://novaexchange.com/addnodes/VGC/

addnode-???

If you don't mind waiting, Novaexchange will (eventually) re-enable deposits. Not sure why they're holding off for so long.

At current market rates 20k isn't worth much. About $6 or $7 USD.

I have got approximately 20,000 VGC that I would like to sell, but cannot find anywhere to sell it. If anyone wants to buy the coins from me, I accept LTC, BTC, and ETH. Thanks.

FYI only your own transactions are saved permanently to your wallet. Pending transactions are stored in memory, so they will be lost when you close the client. There's no persistent storage of other people's pending transactions.

The only way to remove stuck transactions is to stop the sender's wallet from rebroadcasting those transactions - so it's the sender that needs to do the salvagewallet trick...

Assuming -salvagewallet found all of your private keys, your transactions should be properly matched up as you sync. I don't know if -salvagewallet recovers non-essential metadata, like address labels.

Why did you do a salvage if you're not synced? It's really a last resort thing, not something you'd run routinely. There is a small chance it won't find every private key.

Other coins have functions to export and import wallets, which is a lot less clunky, but unfortunately the code for VGC lacks that functionality.

You are in the right thread.

Hashpower will not move stuck coins. There is a bug in the wallet.

It appears to be a bug in the client - it should not create transactions that are ignored by default miner configs, and tweaking one commandline parameter should not result in other clients rejecting mined blocks - so throwing more hash power at the coin won't clear the mempool.

I've found the sequence of steps necessary to recover 'stuck' funds from a sending wallet. All 3 steps must be completed in rapid sequence. If another node rebroadcasts your stuck transaction at some point, your wallet will pick it up again and you'll have to restart from step 1. Temporarily firewalling the vegascoin client may help with steps 1 and 2, but you will need to connect to peers for step 3.

1. Use the -salvagewallet commandline option to forget the pending transactions.
2. Send the recovered funds to somewhere.
3. Mine a few blocks to incorporate the transactions you just created. This is essential to override the older pending transactions (which use the same funds) that are still sitting in everyone else's mempool.

This is VGC - Vegascoin not VGS - LasVegascoin

I've done some experimenting, and it looks like starting the sending client with the -salvagewallet commandline option will recover funds of transactions which have not been picked up by miners. I had a couple of stuck 5000 VGC transactions myself, and doing this released the funds back to my balance. It works because the salvage will only mark funds as spent if they're referenced in the blockchain; any transactions stuck in the temporary mempool are not part of the blockchain, and so the funds associated with those transactions will be available in your wallet.

The salvage operation will back up your wallet, but I strongly recommend you back up the wallet.dat file before starting the client. Just in case.

---

Okay, it doesn't work so perfectly. The client has subsequently picked up the stuck transactions again, possibly from another node repopulating the mempool. My balance has disappeared again and now the oversized transaction is back in the mempool.   It may be possible to try to send out a new transaction (using the recovered funds) before the stale/stuck ones are picked up again, but the network may see that as a double spend.

Also I looked at the source and it seems transactions are hard limited to a maximum of 100k as a form of DoS protection. I don't know why the client is creating transactions larger than 100k, but that's the way it is. There's probably no way to push the stuck transactions through because they exceed the 100k size limit. The only way for the network to accept them would be to raise the limits in the source code. That means everyone has to upgrade the client; a hard fork.

I managed to mine a long chain of blocks at 28MH/s, clearing the mempool entirely, and was hoping the cumulative work was sufficient to keep it the best chain... but no. For some reason the network (ie other clients) are rejecting the blocks with larger transactions, so I effectively mined on my own fork until my client resolved that. I haven't done anything shifty or unusual that should result in peers rejecting the blocks; all I did was start with -blockmaxsize=300000. Here's where my client realised the network didn't want my 74 blocks.

2018-02-06 10:49:15 REORGANIZE: Disconnect 74 blocks; 380ab0f44ba7c2ac2aeca192db9bd16009902f5eda61dfa30c059ea3b48b8b4b..
2018-02-06 10:49:15 REORGANIZE: Connect 54 blocks; ..20c89bc0543e45a9dbad60c8315318b733fa7cc684f6c05096bc6564396ec2a7


There's now 194 stuck transactions back in the mempool.

The issue is most likely that the client is generating transactions that are larger than the default a miner will incorporate into a block. Miners with default settings will ignore them. That's why they get stuck.

To recover stuck transactions you need to be able to make the client (and eventually, the network) forget about the transaction, so you're able to use those coins again.

Or you need to find a miner that is willing to make config changes to accept those larger transactions. If difficulty drops a little (it's currently 3.x) then I may have a go.

The mempool currently has 210 outstanding transactions, and it's been at this level for at least a few days, probably much longer...


edit: Difficulty has dropped so I'm now trying with larger block sizes. I have bumped it up to 300k and so far it has pushed through 10 mempool transactions. I will periodically increase the block size to try to clear more transactions.

edit 2: #$&#@, all my blocks were orphaned. This is exactly what happened with Fastcoin, which has the same issue with oversized transactions that miners ignore by default. The network seems to reject the larger blocks. Sigh.

thanks for a response bud, i guess ill have to wait and hope if somebody can help with a solution.

That is a big issue with this coin. I have had a few 100k vgc stuck in the blockchain over the years. If you try to send a transaction with too many small inputs then it will get stuck.

If the mining reward has halved to 7.5 per block then you should send no more than 2500 in a transaction after they are mined.

Unfortunately, I have no solution to get them back but other users here might.

Hi, ive got 16156 coins stuck on unconfirmed in my wallet. The mining pool threshold was set at 4500 but for some reason the coins were split into 2 payments instead of max 4500. Is there someone that can help me out? it would be very much appreciated.

There is a GOA coin and Goa is pretty much the Vegas of India.  I wonder if VegasCoin could be updated to be a masternode project which seems to be a more attractive investment vehicle for potential adopters.

Wallet needs the stuck coin issue fixed, so we can send more than 5k at a time without worrying they will get stuck.

If a block explorer gets set up, I will see what I can do to keep VGC listed on the new Nova. The community will need to trade and keep some volume going to keep it listed though.