Posts made by sandwormusmc

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.

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:

@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.

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.

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.

@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 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?

The explorer

First off, thanks to the developers for fixing the major issues recently with synchronization and lame peers. Synchronization that used to take days now took less than an hour.

I still have an issue, though. As a basic period of concept before mining more, I wanted to receive and transfer some feather coins. I did so and have 80 some, which I’ve attempted to send over to Bittrex.

However, and this has been an issue for a couple weeks, the transaction is stuck waiting for confirmation. I’ve waited over 24 hours before, and reset the chain multiple times (which was extremely inconvenient when the sync would take days, not as much, now).

I searched the forums and the closest issue I found was a topic marked solved 2 years ago.

Here is a screenshot of the transaction: