Branched from the WO thread:

All y'all may recall I've been looking to Puerto Rico as a means of reducing capital gains taxes owed (I'm 'Merkin). But I've just learned of another (legitimate - according to IRS) potential route out of the system that may be as interesting:

https://www.forbes.com/sites/forbesdigitalcovers/2018/07/17/an-unlikely-group-of-billionaires-and-politicians-has-created-the-most-unbelievable-tax-break-ever/


This thread is meant for the discussion of this program, and the tax advantages thereof. Think of it as a self-selected 'study group' where we all help each other to understand:
- whether this is a program we each can take advantage of;
- tools for evaluating the scope and amount of benefit; and
- the details of engaging such program.

This is a self-moderated thread. I intend to moderate only posts that are clearly off-topic or abusive. In an ideal world, this would be zero deletions. Let's see how it goes.


Edit: Nevermind - there is already active discussion underway at : https://bitcointalk.org/index.php?topic=4740118.0

Yeah, yeah. Drugs are illegal. But what about mah attempted murder. Whatevs.

But seriously - when you look into the matter, there seem to be very serious issues with Ulbricht's investigation, arrest, trial, conviction, and sentencing. As in - issues that are likely appropriate to have addressed by the United States Supreme Court.

Downsize DC and its sister organization Zero Aggression Project have had recent success in getting the USSC to move the needle on recognition of freedoms. Typically working through the amicus (i.e. 'friend of the court') process, their arguments have even provided novel views that have been the hinge upon which several USSC cases have overturned lower miscarriages of justice.

Downsize DC intends to file an amicus brief in the Ulbricht case focusing on two specific issues:

4th Amendment - Does the government have a legitimate interest in warrantless suctioning of all your phone and internet traffic?

6th Amendment - Does a sentencing judge get to increase sentence guidelines on the basis of allegations never argued in court?

Downsize DC is a tiny but effective organization. They can use your help. If you value liberty, please throw them whatever dollars you can afford. You can earmark it for this amicus brief. And if you donate through ZAP (assuming you are US-ian), you can deduct the contribution on your taxes.

More info: https://downsizedc.org/silk-road-amicus/

Silk Road aside, these are important issues for any Internet or phone user in America.

...starts today.

Good, good... let the FOMO flow through you.

Judge for yourself whether or not this has anything to do with "Wall Observer BTC/USD - Bitcoin price movement tracking & discussion", as per the title of the thread from which it was deleted.

Feel free to add your own deletions here. This is a self-moderated thread, which I think means mods will treat it as hands-off. I will delete commercial spam if any. Otherwise, hands-off - as long as it pertains to stuff deleted from the WO thread.

A reply of yours, quoted below, was deleted by the starter of a self-moderated topic. There are no rules of self-moderation, so this deletion cannot be appealed. Do not continue posting in this topic if the topic-starter has requested that you leave.

You can create a new topic if you are unsatisfied with this one. If the topic-starter is scamming, post about it in Scam Accusations.

How about nodes? Does BCH actually have any that aren't Bitmain?

I cannot speak definitively. There's mine. I ain't Bitmain. I assume that many others -- who I know to believe in the direction Bitcoin Cash has set for Bitcoin's future -- likewise run nodes.

Not much of an answer, that. Sort of hand-wavey.

I agree. Of course it is hand-wavey. What do you want me to do? I have no definitive list of all nodes. Do you have one for Bitcoin Segwit? Tallying them up -- in a permissionless environment -- would seem to be the responsibility of the person desiring the statistic, no? I guess in this case, that would be you. Right?

Perhaps if you could make a cogent case showing how Bitcoin Segwit is in any way more decentralized than Bitcoin Cash, you might have a point. But so far, all I've seen from you or others is mere hand waving.

Node count and distribution is important. Why are you pretending it's a non-issue?

I am not pretending it is a non-issue. I assume there are currently fully-validating non-mining 'nodes' in sufficient number. I am also assuming as people who operate fully-validating non-mining 'nodes' shift from focused upon Bitcoin Segwit to being focused upon Bitcoin Cash, that they will start operating 'nodes' upon Bitcoin Cash. Does this seem unreasonable to you? If so, why?

Of course, it is true that I have much less regard for the operation of such non-mining, fully-validating 'nodes' than do most. Indeed, I believe they provide essentially zero benefit to the system as a whole (though they do provide some measure of benefit to their individual owners).

Further, I believe that any system that does not provide forcible barriers to entry is decentralized to the extent that it need be. If the decentralization is purported to 'keep another class of parties in check', then spinning up a single said decentralizing element is sufficient to perform the task at hand. The system need not depend upon ridiculous oversubscription to perform the requisite function.

So presumably, that was your best 'cogent case showing how Bitcoin Segwit is in any way more decentralized than Bitcoin Cash'? What else ya got?

(apologies for the somewhat aggressive tone)

OUR SEVEN SOCIAL PRINCIPLES:
WE ASSUME GOOD FAITH.
WE REWARD THE POSITIVE.
WE ACT WITH DIGNITY.
WE TRUST EACH OTHER TO FAIL WELL.
WE DO NOT ASK PERMISSION.
THE NETWORK IS MOTHER, THE NETWORK IS FATHER.
WE HAVE FUN, BECAUSE IT ATTRACTS MORE PEOPLE.

drugs are bad mmmmmmkay?

OTOH, vision statements are usually good. mmmmmmkay?

10.600 BTC sell wall on Bittrex, @ 0.1 BTC/BCH

Edit: probably Roger Ver's last stash in this pump.

Probably not. I've been trading 10 BTC per day into Bitcoin Cash most days for the last few weeks. I ain't outta ammo yet. And I'm just an itty-bitty minnow.

BCH doesn't give to users anything that BTC doesn't!

Well, other than affordable and fast transactions. Oh - it also gave better than 100% in the last few days. Bitcoin Segwit? Not so much.

Cheers!

BTC actually has significant advantages over Bitcoin Cash, even if it has higher fees and transaction times, simply because it's the common denominator for literally every altcoin.

True statement. At least at this moment in time. Don't get too cocky now.

BCashers got rekt.

In whatever bizzaro universe better than doubling your money (closer to 4x) in the last few days can be considered 'rekt'.

Replaced. Go here: https://bitcointalk.org/index.php?topic=2402558.0

Sorry - error in thread creation.

[nano used the change output from the first unconfirmed tx as one of the inputs to the new tx!]

So I am a n00b as regarding as Ledger nano s operations. I am transitioning from an Armory Offline solution for my cold storage to Ledger. I hit a stumbling block, and seek info.

Yesterday, I funded an exchange account with a send from Ledger. I used the standard fee as suggested by nano. Unfortunately, it was not enough for quick processing. Fair enough, my bad.

Today, seeing the tx did not go through, I created another tx to the same send address. IOW, once both the previous tx and this one clear, I will have double the amount sent in either single tx. I used the high fee option presented by nano. My expectation was that this tx would clear promptly, and the first tx would process at some later time.

I checked the new tx on blockchain.info. Imagine my surprise when I saw that nano used the change output from the first unconfirmed tx as one of the inputs to the new tx! 

Is there some way to configure nano to prevent this from happening?
A setting to just plain prevent this?
A setting to issue a warning requiring confirmation before this can occur?
Coin control options so I can select which inputs will go into any given tx?

[What is Bitcoin GPU?]

I honestly don't know much about this coin. I'll just try to honestly represent what is available elsewhere on this coin.

People are stating to inject this into discussions on Bitcoin Cash. This is a thread where such folk can be sent for more meaningful discussion on BitcoinGPU.

Initial probe (?): https://bitcointalk.org/index.php?topic=2046790.0

Website: http://btcgpu.org/

The website indicates that BitcoinGPU is to be forked from Bitcoin Genesis at the same block height that Bitcoin Cash forked (478558). I can not yet find evidence of a single mined block. I may be missing it. Please respond below if you detect a BitcoinGPU block at height 478559 or higher.

<editeditedit>
From downthread:
The main website has now been updated http://btcgpu.org/ and the fork block has been set at #491407
(not vetted)
</editeditedit>

Website snapshot:


[About UAHF] [Source Code] [View Specs] [Download Binaries]

<<logo>>

An implementation of Bitcoin peer-to-peer electronic GOLD.
Learn about Bitcoin GOLD

What is Bitcoin GPU?
Bitcoin GPU is a full node implementation of the Bitcoin protocol.
GPU mining can protect Bitcoin Key value: Decentralize.

ROADMAP
Once Bitcoin ABC forked Bitcoin, BTCGPU will be activated at the same time.
It will be 1M+SW .
when the block size is full again, will en-crease  the block size to 2M，4M...
When mining?
When code development is done, starts to mining.
The developer is working hard on it.
It will support original smart contract.
If needed, hard fork again to support original smart contract.
not side chain smart contract.

ICO
BTCGPU will create 16000 blocks after forked from No 478558th Blcock.
every block 12.5 BTG.
it will be sold to ico investor.
1BTC=10BTG.
this ICO will help BTG chain the longest Bitcoin blockchain.
all rised BTC will used to hire developors, advertisement, etc.

ROBUST
A fork of the stable Bitcoin Core, Bitcoin GPU aims to build on this base with improved code quality. Development follows a process of continuous integration, based on industry best-practices.

SCALABLE
Bitcoin GPU implements the UAHF (User Activated Hard Fork) proposal to accept GPU mining. Miners can choose the size of the blocks they want to mine, with a default of 1 MB. It includes replay and wipeout protection.


MODERN
For too long, Bitcoin has been held back by the centralize mining industry. GPU brings Bitcoin into the modern age with an exciting technological roadmap to enable massive on-chain scaling well into the future with decentalize.

[About UAHF] [Source Code] [View Specs] [Download Binaries]
[Additional Downloads: Ubuntu Packages]


note: all links tie right back to this very landing page.

So we have some upcoming events in Bitcoinlandia that may result in hard forks of the Bitcoin blockchain. If the blockchain indeed forks, then anyone showing a balance of X on the blockchain immediately before the fork will -- after the fork -- have a balance of X coins on each of the resultant chains.

There are several approaches an exchange might take to this event. The approach that customers would deem preferential is to reflect these chains such that each customer maintains their full balance on each of the chains. But the exchange may toss the coins on one or other chain, keep the coins on one of the chains for themselves, or perhaps several other approaches.

I have been looking around the coinbase.com and gdax websites looking for a concrete statement of how they will handle any Bitcoin chain split. I have however been unable to find this. They wrote back in March that they are leaving their options open. However, since March, the probability of a Bitcoin chain split has likely risen by an order of magnitude or more.

Has anyone seen a recent statement of how they will handle such a split?

So I'm running a Cold wallet on an airgapped machine. I've generated a Watch-only wallet on a networked machine. These have been running for some time.

Today, I notice that the Watch-only wallet has addresses that the Cold wallet does not seem to know about. At least I cannot seem to get the Cold wallet to display these addresses.

As addresses are deterministically-generated (right?), there should be some way to induce the Cold wallet to generate the same addresses as the Watch-only wallet (right?).

How do I make the Cold wallet display the complete set of addresses - for example, in order to sign a message from those addresses?

- Napoleon Bonaparte

I wish to air posts that -ck inexplicably excised from his/her thread "The Barry Silbert segwit agreement with >80% miner agreement."

Of course, that is a self-moderated topic. I am accordingly not making any claim that excising my posts was illegitimate. But custom typically allows for any posts that at least remain on topic. Was I? You be the judge.

This seems to be the one that metaphorically broke the camel's back:

BU ... It's totally irrelevant to this next round of clashes.

As the data shows, it has the largest signaling support. Ergo, it is quite central to the ongoing debates.

Fine, believe what you want and I'll chalk it up to faith and put you back on ignore.

As you wish - it's a free internet.

Though I must confess some bemusement - especially in light of the fact that it certainly seemed to me that -- until our discussion -- you were totally unaware of the implications of parallel validation upon mining dynamics. (implementation shortcomings notwithstanding)

As a sidebar comment, I guess -ck was merely kidding about putting me on ignore.

Here's the preceding message, which seems to have gotten under -ck's skin. While it was a reply to gentlemand rather than to -ck, it reiterated a point of discussion I had made several posts back. And included updated data on the topic of discussion. Which has direct bearing upon the topic of the thread title (that whole >80% miner support ... umm ... manifest untruth):

That's what squishalised Unlimited in the end.

I like the word 'squishalised'. But I do not think that word means what you think it means.jpg. Just now:



BU still #1 in miners signaling support.

And the last one follows. I guess this could arguably be deemed off-topic. As could perhaps any of the other dozens of posts in the thread that centered upon UASF:

Remember that VIAcoin didn't look at what segwit actually does months later after FUDding it.

Hmm. WTF is VIAcoin?

Well then brace for impact because UASF is coming. Segwit is getting in like it or not.

Segwit has already gotten in. If you want Just Another Shitty Segwit Altcoin, be my guest.

Thanks for listening. I'm ready for the expected attaboys and expected pummelings from the expected tribes respectively (albeit with no expectation of respectfully)...

Some time back, I created my Cold Storage mechanism based upon Armory 0.88.1-beta. Somewhere along the line, I upgraded the online watching component in order to allow continued use of a hot wallet on the same system. Now I want to dip into my Cold funds, but find myself unable to. Upon creating the transaction, I get:

Code:

*Version Warning*
<!>
Since Armory version 0.92 the formats for offline transaction operations has changed to accommodate multi-signature transactions. This format is _not_ compatible with versions of Armory before 0.92.
To continue, the other system will need to be upgrades to to version 0.92 or later. If you cannot upgrade the other system, you will need to reinstall an older version of Armory on this system.

OK, this all seems clear enough. What I don't know is whether I can freely mix and match versions. Is the logical route forward just to upgrade the Offline Signing machine to the latest and greatest Armory? Will they interoperate then?

Offline Signing:
Armory 0.88.1-beta
ubuntu 12.04 LTS

Online Watching:
Armory 0.93.2
Mac OS X 10.8.5

Any gotchas on the install? Or can I just install it in place, over existing version?

I am decommissioning an old phone. While I can just send bitcoins out to an address generated by other wallet, that works only for the stored funds themselves. I would like to also save the transaction history. Is there an option for generating a .csv or similar from the transaction history?

Like the title says. The current iteration of The SegWit Omnibus Changeset does not fix the O(n^2) hashing problem. At least according to Peter Todd:

We haven’t actually fixed the O(n²) signature hashing problem yet, although we’re fairly confident that we can, and there’s a open pull-req implementing the cache that we need.

- https://petertodd.org/2016/segwit-consensus-critical-code-review

Not necessarily an insurmountable problem. And I suppose PT might be... err... uninformed. However, it certainly puts some specious claims (e.g., April; e.g. safe scaling) into perspective. One wonders what other major claimed features of The Omnibus SegWit Changeset remain technical pauperism.

Might be worth a discussion, donchathink?

Hey - it's crypto.

RSA 2016 The Association for Computing Machinery used the RSA 2016 conference to announce the winners of its annual Turing Award: encryption wizards Whitfield Diffie and Martin Hellman.

"Naturally I'm thrilled by this by this award, but thrilled for cryptography," Diffie said. "It's the third time the Turing award has been given to cryptographers. The fact that it is so central to the field is amazing."

Diffie and Hellman published their seminal paper New Directions in Cryptography [PDF] in 1976 and it outlined the first public-key cryptography system, allowing people to encrypt data using publicly exchanged keys and decrypt information using their secret private keys.

...

http://www.theregister.co.uk/2016/03/01/diffie_and_hellman_scoop_turing_award_for_key_work_on_crypto/

Purportedly Patrick Byrne's twitter account:

https://twitter.com/OverstockCEO/status/628567358219657216

If real, I find this very exciting. The linked website however, is devoid of anything sans logo and mechanism for signing up for a spam list has gone live since this post was first made:

http://t0.com/

Anyone have any more details?

News a month ago was that he was planning on launching a securities exchange (a la NYSE, NASDAQ, or similar) where all trades happen on the blockchain. More specifically, on the Bitcoin blockchain.

"Though Byrne originally told WIRED the bond would not be issued on the blockchain proper, it indeed will."

- http://www.wired.com/2015/06/overstock-will-issue-private-bond-powered-bitcoin-tech/

Byrne's a rockstar. From exposing the nefarious issuances of naked shorts on the major trading platforms, to an early rollout of Bitcoin acceptance for a vast catalog of internet order products.

I am very interested to see where this goes.

http://money.cnn.com/2015/07/08/investing/nyse-suspends-trading/

Anyone with the inside scoop?

Meanwhile in crypto-land:

While we've been distracted by little ol' Greece (with ~0.3% WDP), China's stock markets have lost $USD trillions in the last month!

Yeah, slipped under my radar too. Discuss amongst yourselves while I go read some...

[Top Post Edit: Goal Met.]

Top Post Edit: Goal Met.

As of 2015 Jun 15, we have hit the goal of $600.00 (the stated approximate confiscation by the jackboots). Thank you all for your donations.

I'll update the donator's list with what I can sort out, provide pictorial proof of existence of Federal Reserve Notes, with 'kicker' paper wallet including prominent funding address, and deliver all the above to Zoe in the next day or three.

In the meantime, see today's postings in this thread for suggestions for an inscription to include.

Thanks to everyone who selflessly pitched in. And thanks to Gleb for kicking this whole project off.

It'll be up to Burt and Jean as to whether there will be a public acknowledgement of this gesture. But Jean has posted contact info at BurtW.com - you can always ask if you suspect anything might be amiss.

Watch this space for the next step...

OK, 2015 Jun 16 update. Stop donating to original address. Any further donations should be sent to https://blockchain.info/address/1KayK9cRSUHXLcs3kjyu1sbcJpUrdsk2Ei, which is a paper wallet that will be given in paper wallet form, along with the cash raised.


Please see the 'BurtW arrested' thread (link below) for background.

https://bitcointalk.org/index.php?topic=934268.msg10733040#msg10733040

Summary: In its bloodlust to lash out at a person trading bitcoins for their personal use, the behemoth of the state has stolen assets of an innocent family. Caught up in this is the family's eight year old daughter - the jackboot thugs stole her piggy bank, along with approximately $600 -- her entire life savings.

One would think that, once BurtW is exonerated, Zoe would get her savings back. But the tyrants are employing the legalistic theft doctrine of so-called 'civil forfeiture' to simply steal the funds, which leaves no meaningful recourse for recovering the funds. Easy as stealing candy from a baby. (no shit - look it up if you're not familiar with this travesty of injustice).

Bruno has suggested a donation fund, with the goal of restoring young Zoe's hard-earned money.

Having lived the nightmare of dozens of masked men, bearing guns and full riot gear, burst into her home and abuse and terrify her family, Zoe may never again trust anyone in law enforcement. However, we may be able to restore a little of her faith in the basic goodness of most of humanity.

If you're up to the task, would you be so kind as to escrow a bitcoin wallet address that you'll create for the purpose of garnering $600 USD worth of bitcoins? Once amassed, you convert (or however) the bitcoins to fiat, and source a like or similar container/safe that said amount once held Burt and Jean's eight-year-old daughter's savings to once again store the $600.

Hey Bruno - I'd be happy to do so. Bear in mind that, despite my long time involvement here on bitcointalk, I have never escrowed anything for anybody. Accordingly, there is the issue of having to trust me.

Alternatively, we could create a multisig address, which would distribute the trust. However, that's another thing that I've never done, and it would take a bit for me to figure it out. This time could run in parallel with a discussion of whom within the community should be signatories (keyholders) to the multisig address.

Thirdly, we can employ kevinlarr's addy. But then the community would need to trust both of us. In this case, it is likely better to leave it in the sole custody of kevinlarr, though I could still ensure the fiat gets to Zoe. Incidentally, while I have met Zoe -- even bought girl scout cookies from her on more than one occasion -- I am unsure of the spelling of her name. However, I have no reason currently to think that is is other than the most common 'Zoe' derivation.

So I ask anyone likely to donate to weigh in -- in this thread -- on which of these options they would prefer.

==========================
Edit:

Following is the address for donations - see https://bitcointalk.org/index.php?topic=985596.msg10752541#msg10752541 for details.

1FvX81SxjLLvFymFVDH3Z4LXA87jVU6EaH OK, 2015 Jun 16 update. Stop donating to original address. Any further donations should be sent to https://blockchain.info/address/1KayK9cRSUHXLcs3kjyu1sbcJpUrdsk2Ei, which is a paper wallet that will be given in paper wallet form, along with the cash raised.

Donators include:
jbreher
Gleb Gamow
kevinlarr
frankenmint
seven others that have not declared
pawel7777
more unidentified
jonald_fyookball
BitUsher
hedgy73

I am on
Bitcoin Core version v0.9.2.1-g354c03f-beta (64-bit)

On
Mac OS X 10.7.5
2.5 G i7, 16 GB mem

Last night, I fired up Bitcoin for the first time in about a week. It synced some, then got stuck at block 322870.

Quit & restart, stuck at block 322870.

Quit, restart with -reindex - churned for a while then got 'database corrupted' message.

Restored Bitcoin-QT/[blocks chainstate] from about a week ago.

Restarted - churned for a while, now stuck on block 322870.

What's so special about block 322870 that I can't seem to sync past it?

tail of log file:

Code:

  forking the chain at height 322870 (00000000000000001f7bbfa5ab7f7883d372065d6f18c9ab91dcfb891394c8c8)
  lasting to height 323012 (000000000000000019b16f4a6cd8717ab8f4836bbc9822894cc49785badfdaa7).
Chain state database corruption likely.
2014-09-29 04:25:05 ProcessBlock: ACCEPTED
2014-09-29 04:29:42 CheckForkWarningConditions: Warning: Large valid fork found
  forking the chain at height 322870 (00000000000000001f7bbfa5ab7f7883d372065d6f18c9ab91dcfb891394c8c8)
  lasting to height 323013 (00000000000000000057d23bab8b8449858c05fcf70b2079ed233ad6380980a7).
Chain state database corruption likely.
2014-09-29 04:29:42 ProcessBlock: ACCEPTED
2014-09-29 04:43:15 CheckForkWarningConditions: Warning: Large valid fork found
  forking the chain at height 322870 (00000000000000001f7bbfa5ab7f7883d372065d6f18c9ab91dcfb891394c8c8)
  lasting to height 323014 (00000000000000001ae5fbe7ef691842dcea1bdfa037eb137755090e490bcafb).
Chain state database corruption likely.
2014-09-29 04:43:15 ProcessBlock: ACCEPTED
2014-09-29 04:54:38 ERROR: CheckInputs() : tried to spend coinbase at depth 26
2014-09-29 04:54:38 ERROR: AcceptToMemoryPool: : ConnectInputs failed bc1a10b54a024e280d7c309edb8c24e932b7243da28644657bd43540dcef2f82
2014-09-29 04:56:38 ERROR: CheckInputs() : tried to spend coinbase at depth 26
2014-09-29 04:56:38 ERROR: AcceptToMemoryPool: : ConnectInputs failed bc1a10b54a024e280d7c309edb8c24e932b7243da28644657bd43540dcef2f82
2014-09-29 04:58:19 ERROR: CheckInputs() : tried to spend coinbase at depth 26
2014-09-29 04:58:19 ERROR: AcceptToMemoryPool: : ConnectInputs failed a8515c17bd06ab0729ab9a803ec7d6dc1916258c7f4928ddf07b37354d52ae43
2014-09-29 04:58:31 CheckForkWarningConditions: Warning: Large valid fork found
  forking the chain at height 322870 (00000000000000001f7bbfa5ab7f7883d372065d6f18c9ab91dcfb891394c8c8)
  lasting to height 323015 (0000000000000000092e056ab9c5a3242bfa911ba9a0a8a3836bcd4b5fcab2f8).
Chain state database corruption likely.
2014-09-29 04:58:31 ProcessBlock: ACCEPTED
2014-09-29 04:58:37 ERROR: CheckInputs() : tried to spend coinbase at depth 26
2014-09-29 04:58:37 ERROR: AcceptToMemoryPool: : ConnectInputs failed bc1a10b54a024e280d7c309edb8c24e932b7243da28644657bd43540dcef2f82
2014-09-29 05:00:19 ERROR: CheckInputs() : tried to spend coinbase at depth 26
2014-09-29 05:00:19 ERROR: AcceptToMemoryPool: : ConnectInputs failed a8515c17bd06ab0729ab9a803ec7d6dc1916258c7f4928ddf07b37354d52ae43
2014-09-29 05:00:38 ERROR: CheckInputs() : tried to spend coinbase at depth 26
2014-09-29 05:00:38 ERROR: AcceptToMemoryPool: : ConnectInputs failed bc1a10b54a024e280d7c309edb8c24e932b7243da28644657bd43540dcef2f82
2014-09-29 05:02:18 ERROR: CheckInputs() : tried to spend coinbase at depth 26
2014-09-29 05:02:18 ERROR: AcceptToMemoryPool: : ConnectInputs failed a8515c17bd06ab0729ab9a803ec7d6dc1916258c7f4928ddf07b37354d52ae43
2014-09-29 05:02:38 ERROR: CheckInputs() : tried to spend coinbase at depth 26
2014-09-29 05:02:38 ERROR: AcceptToMemoryPool: : ConnectInputs failed bc1a10b54a024e280d7c309edb8c24e932b7243da28644657bd43540dcef2f82
2014-09-29 05:04:18 ERROR: CheckInputs() : tried to spend coinbase at depth 26
2014-09-29 05:04:18 ERROR: AcceptToMemoryPool: : ConnectInputs failed a8515c17bd06ab0729ab9a803ec7d6dc1916258c7f4928ddf07b37354d52ae43
2014-09-29 05:04:37 ERROR: CheckInputs() : tried to spend coinbase at depth 26
2014-09-29 05:04:37 ERROR: AcceptToMemoryPool: : ConnectInputs failed bc1a10b54a024e280d7c309edb8c24e932b7243da28644657bd43540dcef2f82
2014-09-29 05:06:19 ERROR: CheckInputs() : tried to spend coinbase at depth 26
2014-09-29 05:06:19 ERROR: AcceptToMemoryPool: : ConnectInputs failed a8515c17bd06ab0729ab9a803ec7d6dc1916258c7f4928ddf07b37354d52ae43
2014-09-29 05:06:38 ERROR: CheckInputs() : tried to spend coinbase at depth 26
2014-09-29 05:06:38 ERROR: AcceptToMemoryPool: : ConnectInputs failed bc1a10b54a024e280d7c309edb8c24e932b7243da28644657bd43540dcef2f82
2014-09-29 05:08:19 ERROR: CheckInputs() : tried to spend coinbase at depth 26
2014-09-29 05:08:19 ERROR: AcceptToMemoryPool: : ConnectInputs failed a8515c17bd06ab0729ab9a803ec7d6dc1916258c7f4928ddf07b37354d52ae43
2014-09-29 05:08:38 ERROR: CheckInputs() : tried to spend coinbase at depth 26
2014-09-29 05:08:38 ERROR: AcceptToMemoryPool: : ConnectInputs failed bc1a10b54a024e280d7c309edb8c24e932b7243da28644657bd43540dcef2f82
2014-09-29 05:10:19 ERROR: CheckInputs() : tried to spend coinbase at depth 26
2014-09-29 05:10:19 ERROR: AcceptToMemoryPool: : ConnectInputs failed a8515c17bd06ab0729ab9a803ec7d6dc1916258c7f4928ddf07b37354d52ae43
2014-09-29 05:12:19 ERROR: CheckInputs() : tried to spend coinbase at depth 26
2014-09-29 05:12:19 ERROR: AcceptToMemoryPool: : ConnectInputs failed a8515c17bd06ab0729ab9a803ec7d6dc1916258c7f4928ddf07b37354d52ae43
2014-09-29 05:14:41 CheckForkWarningConditions: Warning: Large valid fork found
  forking the chain at height 322870 (00000000000000001f7bbfa5ab7f7883d372065d6f18c9ab91dcfb891394c8c8)
  lasting to height 323016 (000000000000000010807c7fcd7d76520353fb79562e155126cdd6e412742c96).
Chain state database corruption likely.
2014-09-29 05:14:41 ProcessBlock: ACCEPTED
2014-09-29 05:15:16 ERROR: CheckInputs() : tried to spend coinbase at depth 67
2014-09-29 05:15:16 ERROR: AcceptToMemoryPool: : ConnectInputs failed 64183b9ea2f93dd8a48ab61a699dd34fb21440badbe885d91d49ead73a9aa46b
2014-09-29 05:17:15 ERROR: CheckInputs() : tried to spend coinbase at depth 67
2014-09-29 05:17:15 ERROR: AcceptToMemoryPool: : ConnectInputs failed 64183b9ea2f93dd8a48ab61a699dd34fb21440badbe885d91d49ead73a9aa46b
2014-09-29 05:19:15 ERROR: CheckInputs() : tried to spend coinbase at depth 67
2014-09-29 05:19:15 ERROR: AcceptToMemoryPool: : ConnectInputs failed 64183b9ea2f93dd8a48ab61a699dd34fb21440badbe885d91d49ead73a9aa46b
2014-09-29 05:21:15 ERROR: CheckInputs() : tried to spend coinbase at depth 67
2014-09-29 05:21:15 ERROR: AcceptToMemoryPool: : ConnectInputs failed 64183b9ea2f93dd8a48ab61a699dd34fb21440badbe885d91d49ead73a9aa46b
2014-09-29 05:22:14 CheckForkWarningConditions: Warning: Large valid fork found
  forking the chain at height 322870 (00000000000000001f7bbfa5ab7f7883d372065d6f18c9ab91dcfb891394c8c8)
  lasting to height 323017 (00000000000000001ab82f6e47b65eaf58f2df3b2bf50663aad70b9619691fd5).
Chain state database corruption likely.
2014-09-29 05:22:14 ProcessBlock: ACCEPTED
2014-09-29 05:22:54 ERROR: CheckInputs() : tried to spend coinbase at depth 45
2014-09-29 05:22:54 ERROR: AcceptToMemoryPool: : ConnectInputs failed 5f4545d58667d0b8a9637698529f3146688a7ef53d62262cf642a5bd3bb0eaa3
2014-09-29 05:23:15 ERROR: CheckInputs() : tried to spend coinbase at depth 67
2014-09-29 05:23:15 ERROR: AcceptToMemoryPool: : ConnectInputs failed 64183b9ea2f93dd8a48ab61a699dd34fb21440badbe885d91d49ead73a9aa46b
2014-09-29 05:24:53 ERROR: CheckInputs() : tried to spend coinbase at depth 45
2014-09-29 05:24:53 ERROR: AcceptToMemoryPool: : ConnectInputs failed 5f4545d58667d0b8a9637698529f3146688a7ef53d62262cf642a5bd3bb0eaa3
2014-09-29 05:25:15 ERROR: CheckInputs() : tried to spend coinbase at depth 67
2014-09-29 05:25:15 ERROR: AcceptToMemoryPool: : ConnectInputs failed 64183b9ea2f93dd8a48ab61a699dd34fb21440badbe885d91d49ead73a9aa46b
2014-09-29 05:25:54 CheckForkWarningConditions: Warning: Large valid fork found
  forking the chain at height 322870 (00000000000000001f7bbfa5ab7f7883d372065d6f18c9ab91dcfb891394c8c8)
  lasting to height 323018 (000000000000000017363b882751f64830786000e1d2ea1b59cce501354074a6).
Chain state database corruption likely.
2014-09-29 05:25:54 ProcessBlock: ACCEPTED
2014-09-29 05:26:53 ERROR: CheckInputs() : tried to spend coinbase at depth 45
2014-09-29 05:26:53 ERROR: AcceptToMemoryPool: : ConnectInputs failed 5f4545d58667d0b8a9637698529f3146688a7ef53d62262cf642a5bd3bb0eaa3