Sending from android wallet, most recent update, stuck waiting for confirmation
-
I forgot to mention, I checked the block explorer and didn’t see the send transaction show up. I don’t know of any alternative wallets other than the android one (witch sends seem to be broken for), the mac one (which suffers from the same sync issue android used to, it’s been syncing for days now), and the Linux wallet won’t install or compile in Fedora 26. So… I’m stuck?
-
I have tried to send coins to and from my Android wallet and it worked without any problems.
What I can see in your screenshot is, that the size of the transaction is very high (length=76263)
Transactions of this size have problems to make it into the block chain.
Based on the size of the transaction, I assume you try to collect mined coins from a pool and have bound a lot of small amounts of coins into one large transacion.
I’m not sure about the maximum transaction size for the Feathercoin BC at the moment, but can you try to send the coins in a smaller transaction with size of 7-10k only? simply try to send just one FTC or so to verify the wallet itself is working, and it is a problem of the BC.
We may need to add a warning about large transaction sizes to the wallet.By the way this problem is common to all coins.
Another try would be to increase the transaction fee.
-
Is it stuck waiting confirmation at Bittrex? What is the address? What fee did you set? So we can follow it and see what happened …
-
@Wellenreiter that’s true, I mined from a pool and received incremental pay outs in small pieces, however those should all be their own transactions, though that’s an implementation detail I’m not fully aware of. I just mined 87 or so FTC, then tried to send the balance to Bittrex. The only other coin I’ve sent such large amounts of was Pirl (about 20) and XDN (~57). Those went through without issues. I’ll try your suggestion of sending in smaller pieces, first with a 1 FTC transaction to test.
@wrapper the fee I set was 0.1 (default?). I did not see any pending transaction on the Bittrex side.
For what it’s worth, the small transactions are all confirmed, so I’m not totally sure whay you mean by bundle then into one transaction, those souls be there already. Again, an implementation detail that perhaps an end user would/should not be aware of. Perhaps you’re right and a warning should come up for transactions of a certain amount.
-
I had the same issue sending “dusty” payments of PXC. The Blockchain code calculates the fee on the size in kilobytes. Where there are multiple inputs this can result in an increased fee. Whereas the desktop wallet might calculate that - you may have set low fee set on the phone. It should be 0.01 FTC, by the way, 0.1 is a high fee.
For anyone who hasn’t mined, p2pool in particular, can result in a large number of small payments. Documenting these results in multiple address, or size to make the transaction.
However, I was able to send 100s of (input) transactions, with a normal fee plus 2 or 3 times for the extra space. That would be difficult with just 87 FTC, unless it is made of ~1000s payments, i.e. very dusty.
It may be that some of them are less than dust level, and that has caused an issue.
Although you didn’t give the address so we can’t check the explorer without typing it in from your screenshot, it currently looks like it isn’t being sent.
Here is a Bitcoin transaction with 7.6KB size, showing it is not excessive inputs. 76 kb would be 10 times the inputs.
https://www.smartbit.com.au/tx/602d2a32c36b518a0c2c9d4916732d3aedf848a76c6fcb740b6393d51b5c349f -
the mecahnism for sending coins is, that if you have 100 little payments received and use them to send one large payment, the corresponding transaction needs to have 100 inputs, what increases the size needed in the block chain to add the transaction.
You can see the inputs on the left side of the page wrapper mentioned.
All this is contained in the transaction.This functionality is implemented in all coins and allows to track each coin or fraction of a coin back to the block it was mined with.
-
Fair enough. My android wallet has resynced now and I’ll give it a shot.
Here is the wallet address (you could have also gotten it from the block explorer link I pasted in the first post).
6h2ptNRuwAEqkW2AWBvAuNSrDY9P9WN6Ah
Now that I’ve resynced I’ll try it a 1 FTC send to Bittrex.
By the way, thanks for being so responsive, great so far.
-
Sorry I didn’t find that link, and the receiving address 6v …
http://explorer.feathercoin.com/address/6h2ptNRuwAEqkW2AWBvAuNSrDY9P9WN6Ah
-
No worries. Unfortunately after resetting the chain the transaction appeared again, so my wallet balance is at 0 once more. I’ll try another reset and set a miner to try and mine some more.
-
Ok, keep us informed. Can you post the recieving address? 6v …
-
@wrapper the receiving address was 6vfLUhoNZQAsegnaxQuUYjJsLvtnrYZckc
A second blockchain reset removed the 87 FTC transaction and I sent a 1 FTC test to the address above, which went through easy and is now showing pending on my Bittrex wallet.
I mentioned I used a 0.1 fee after a reset (initially I didn’t know about reset, so I uninstalled and reinstalled) because the default appears to be 0.01. Even then, with a higher fee, I guess the many small pool rewards make transferring potentially difficult. I’m now using p2pool.neoscrypt.de, and since I only have 3 GPUs pointed at it, am getting rewards of ~0.09 FTC every so often.
Perhaps there is some updates that can be done on the p2pool side that can set a minimum payout amount to reduce these kind of dusty payments? My thought here is that to increase adoption for small timers like me with a limited number of rigs, it could make things easier for new miners to join in. I’m guessing there could be some other benefits behind the scenes as well. Anyway, just a thought, I’m not even sure if you are the team behind p2pool or have a hand in that.
-
I successfully sent a 10 FTC transaction as well, took about 10 minutes to go through. Length on that one was 8805. The more I can transfer and the less fees I can pay, the more profitable the mining is, of course…
Thanks for the great support. :smiley:
-
I sent another 15 FTC transaction, and that one seems to have a length of 16k, which has sat for about 15 minutes in “This payment has not been transmitted yet”. I’ll be patient with that one before resetting, but at the moment with 0.09 FTC pool rewards, 10 FTC seems to be the sweet spot for relatively quick transmissions.
-
@sandwormusmc said in Sending from android wallet, most recent update, stuck waiting for confirmation:
@wrapper the receiving address was 6vfLUhoNZQAsegnaxQuUYjJsLvtnrYZckc
A second blockchain reset removed the 87 FTC transaction and I sent a 1 FTC test to the address above, which went through easy and is now showing pending on my Bittrex wallet.
Perhaps there is some updates that can be done on the p2pool side that can set a minimum payout amount to reduce these kind of dusty payments?
This is difficult to do in the no trust required shares system. It would need to run wallets to store shares longer.
I have suggested the solution is to have “coloured pools” i.e. Smaller p2pools, so the payments arn’t so dusty. Perhaps the have a maximum number of contributers.
It would mean waiting longer between payments. But each coloured pool could have differen’t settings, for example 48 hour stratum so people could mine during night rate electic pay levels and retain their stratum over the day.
Coloured p2pools would require some settings and “versioning” of the current codebase.
-
@sandwormusmc said in Sending from android wallet, most recent update, stuck waiting for confirmation:
Perhaps there is some updates that can be done on the p2pool side that can set a minimum payout amount to reduce these kind of dusty payments?
Unfortunately this is not possible, as p2pool does not use miner accounts to collect payouts. Whenever a block is found by the pool all miners participating get their share of the coins based on the hashes they contributed to find the block.
