I got my first payout from extremepool about an hour after the 60 confirms.  However, now, 9 hours later, I find an amount in my wallet only 1/3 of what the pool says has been paid.  If it were simply a matter of a one hour delay, the fraction would be much higher than this.  Rather, there is a widening gap.

Monero had an issue early on with the wallets not adding a txfee by default, so transactions were getting ignored and not added to blocks.  Possibly these pools are not attaching txfees?

Good luck with Duck, friends.  Back to Monero for me.

Thank you for attempting to provide some answers, but I'm afraid my curiosity is not yet satisfied.  I found an obscure link in the OP, http://ducknote.org/aboutduckNote, and in it one obscure footnote that says the block reward can vary, apart from halving:  "*Supply chart has an accurate, but approximate values, because block reward for some blocks can be lower than base reward due the big sized block penalties."

That's not much of an explanation; a proper explanation would address why large blocks are penalized, what the reward variance can be, and how often it might be expected to happen.  By observation, the answer to both the latter two is "a lot".

You say "white papers"--could you perhaps provide more clues as to where additional writings reside?

As to block chain sync being the reason for non-existent or slow payment, I don't think so.  My wallet and the pool are reporting the same block height.  I think that extremepool is not actually paying out right now, and that it is likely not something nefarious, but rather that something is broken.

I'm curious that extremepool.org shows I have a Total Paid, but my wallet shows a zero balance after refresh.  It hasn't been very long, but my experience with XMR on a couple different pools was immediate.

I'm further curious as to why the block reward is not always 320000, but usually some much smaller amount.

Didn't work.  It processes blocks quickly up until 12435 and then starts complaining about orphan blocks and misbehaving nodes.  It appears that, in the opinion of the client as it currently exists on github, the blockchain is corrupt.

Dev...could you please do a fresh compile and install on Linux and check this out?

Can't sync.  Stuck at block 12435, 8 hours back.

Linux, compiled from git.

I did all the addnodes...what to try next?

Thanks...that worked, even though I am on 0.8.8.1 and logs showed the tx fee was correct.  I suspect, in my case, internet connectivity issues caused the daemon to get into a bad state.

No, I am using simplewallet on Linux.

I found this in simplewallet.log:

2014-Jun-14 14:10:03.214535 Transaction successfully sent. <<862ea2494a717bf77c127a2677797ef8faac480676a05a85592d42da2fb01423>>
Commission: 0.005000000000 (dust: 0.000000000000)

So it's not an issue with the fee.

Also in simplewallet.log, just before the above, is:

transaction <862ea2494a717bf77c127a2677797ef8faac480676a05a85592d42da2fb01423> generated ok and sent to daemon, key_images: [...


But the transaction id does not appear in bitmonerod.log

No...since it doesn't show up in the block explorer, I can't imagine what they would be able to do about it. 

So I sent 1 XMR from my wallet to poloniex two days ago, and it has not shown up.

I am on version 0.8.8

I receive payments from moneropool.org fine.

My command was of the form "transfer 2 xxxxx 1 xxxxx"

The wallet responded "Money successfully sent, transaction <xxxxx>"

"payments xxxxx" where "xxxxx" is the payment ID gets "No payments with id <xxxxx>

I tried "payments" again after a refresh and got the same result.

Neither the transaction id nor the payment id show up in bitmonerod.log, nor in monerochain.info.

My balance is indeed one coin short.

I lost net connectivity for a while right after the payment was made.


Suggestions, please?

Something is odd about suprnova, though...all my coins there are still unconfirmed even though younger solomined coins are confirming.

Thanks for taking over UVC!

I just donated 250UVC to each fund.  However, I had to go searching the thread to find out how.  I suggest adding a prominent link to the website on the first page of this thread.

That's right.  Don't ever overwrite or delete or otherwise lose your wallet.dat, and also copy it somewhere safe as a backup.  Your coins are not "in" your wallet.dat, they are recorded on the blockchain.  But the only way to access them is via the private keys in wallet.dat.

Dev:  Evidently, if one uses a port number with myAddress, one should not include the port number on the hallmark generator page.  I suggest you add this to your instructions, and put an error check into the hallmark generator.

While true that a minimum coin price is one satoshi on a BTC exchange, the truism is meaningless.  You have to have people wanting to buy at that price.  What good is a "value" of 1 sat if nobody is willing to buy?  I have seen coins go to one sat and shortly thereafter the buy order book dries up.  GPUC and HEX are examples that come to mind.  After that, they are only able to trade on other markets such as LTC, or get delisted entirely.

So, there is really no such thing as a 1 sat minimum price.

Very sorry to hear that.  Condolences and best wishes.

Hours for POS to start?  That seems...awkward.  No further transactions will go through until we have block 7201 and beyond, right?

My sentiments entirely, as to the absent dev.

However, there is no need to be overly dramatic.  The Coinano exchange is still operating, as are several pools.

OK, great!  That's 3X the original bounties, people...  Spread the word!

30,000 10,000 kFC - 1st Futures Market
15,000 5,000 kFC - 1st Exchange
12,000 4,000 kFC - 2nd Exchange
6,000 2,000 kFC - 1st article @ any major cryptocurrency/finance site
3,000 1,000 kFC - 2nd article @ any major cryptocurrency/finance site
7,500 2,500 kFC - 1st block explorer (note: must be able to read maturity time)
3,750 1,250 kFC - 2nd block explorer
3,000 1,000 kFC - 1st Maturity Switching Pool (any algo)
1,500 500 kFC - 2nd Maturity Switching Pool (any algo)
1,500 500 kFC - 1st blog review
900 300 kFC - 2nd blog review

...and I'll stipulate that these must be positive blog reviews. 

There doesn't seem to be much interest in doing the bounty work, perhaps because the bounties are too small.  I'll pledge to match the dev's amounts for any and all of them completed between now and one week from now, provided at least one other person pledges the same or more.

Anyone?

I don't see the "kFC" business as an issue.  It is profitable to mine at its current price and that price has been remarkably stable.  If it's true that the vesting scheme leads to better price stability then that is a good thing and could lead to FC becoming a winning coin.

What it does need is more buzz, and involvement of the dev.  The vesting period provides time for that to happen before mined coins hit the market, but it's starting to get a little concerning that none of it is happening yet.

Ideas, anyone?