What's new in Bitcoin 0.9.X ,We ready upgrade

wrapper

Re: Upgrade to Bitcoin Core 0.9.X

The other point is we usually wait for the Litecoin version, and patch with Feathercoin enhancements, are you suggesting moving directly to adding patched to Bitcoin core? That’s a lot more work and more complex to pull off…

Can we hold this off until after we’ve moved to Neo?

lizhi

Are FTC and BTC the same ?

pruned version of CTransaction: only retains metadata and unspent transaction outputs

Serialized format:
- VARINT(nVersion)
- VARINT(nCode)
- unspentness bitvector, for vout[2] and further; least significant byte first
- the non-spent CTxOuts (via CTxOutCompressor)
- VARINT(nHeight)

The nCode value consists of:
- bit 1: IsCoinBase()
- bit 2: vout[0] is not spent
- bit 4: vout[1] is not spent
- The higher bits encode N, the number of non-zero bytes in the following bitvector.
  - In case both bit 2 and bit 4 are unset, they encode N-1, as there must be at
    least one non-spent output).

Example: 0104835800816115944e077fe7c803cfa57f29b36bf87c1d358bb85e
         <><>
         |  \                  |                             /
   version   code             vout[1]                  height

   - version = 1
   - code = 4 (vout[1] is not spent, and 0 non-zero bytes of bitvector follow)
   - unspentness bitvector: as 0 non-zero bytes follow, it has length 0
   - vout[1]: 835800816115944e077fe7c803cfa57f29b36bf87c1d35
             8358: compact amount representation for 60000000000 (600 BTC)
             00: special txout type pay-to-pubkey-hash
             816115944e077fe7c803cfa57f29b36bf87c1d35: address uint160
   - height = 203998


Example: 0109044086ef97d5790061b01caab50f1b8e9c50a5057eb43c2d9563a4eebbd123008c988f1a4a4de2161e0f50aac7f17e7f9555caa486af3b
         <><>
        /  \   \                     |                                                           |                     /
 version  code  unspentness       vout[4]                                                     vout[16]           height

 - version = 1
 - code = 9 (coinbase, neither vout[0] or vout[1] are unspent,
               2 (1, +1 because both bit 2 and bit 4 are unset) non-zero bitvector bytes follow)
 - unspentness bitvector: bits 2 (0x04) and 14 (0x4000) are set, so vout[2+2] and vout[14+2] are unspent
 - vout[4]: 86ef97d5790061b01caab50f1b8e9c50a5057eb43c2d9563a4ee
           86ef97d579: compact amount representation for 234925952 (2.35 BTC)
           00: special txout type pay-to-pubkey-hash
           61b01caab50f1b8e9c50a5057eb43c2d9563a4ee: address uint160
 - vout[16]: bbd123008c988f1a4a4de2161e0f50aac7f17e7f9555caa4
            bbd123: compact amount representation for 110397 (0.001 BTC)
            00: special txout type pay-to-pubkey-hash
            8c988f1a4a4de2161e0f50aac7f17e7f9555caa4: address uint160
 - height = 120891

lizhi

Can we hold this off until after we’ve moved to Neo?

We just make some preparations, pass the boring time :)

ok then :D

lizhi

move this post to Technical Development

lizhi

move this post to Technical Development

lizhi

I push my feathercoin technical architecture. This is a PowerPoint from my tentative plan.

I love the graphics design Liz!

+1

wrapper

I push my feathercoin technical architecture. This is a PowerPoint from my tentative plan.

I also very much like, thanks +1

wrapper

**Just Read this on Github: re: upgrade version 0.9.3 **

Warren Togami to litecoin

You have to understand that there is little point in releasing 0.9.3 as-is merely to match Bitcoin. This is because we worked hard to backport many of the key features of 0.9.x to our current Litecoin release 0.8.7.2 to such an extent that there is almost no benefit in upgrading. If we are going to take the risk of a major upgrade it better add actual features that users really want. At this moment I have 0.9.3 working without any known problems and I am working on backporting the most useful Bitcoin 0.10 features like watch-only addresses. A source-only alpha tree will be public within a few days.

â€"
Reply to this email directly or view it on GitHub.

mirrax

I push my feathercoin technical architecture. This is a PowerPoint from my tentative plan.

Looks great Lizhi. +1

What’s the DPOS?

Also, that should be “Light/Dark Blockchain”

Also looks like Cryptonit will help us implement cross crypto exchange into the QT. The user just needs an account with cryptonit. The affiliate stuff will help feed the community bounty pool. I think they are also offering no fees for ftc withdrawals and deposits…

“If you are serious enough we can thing of removing deposit/withdrawal FTC fees, it will make absolutely free moving FTC coins between actual balance and trading balance.”

kris_davison

Wow that sounds awesome!!

lizhi

If you had to describe feathercoin in one sentence, how would you do it?

I say “new core new dream” :)

lizhi

I hope to finish the 0.9.3 core .

lizhi

Hi I ask for help.When I run feathercoin 0.9.3 core ,I have a assert error.

a assert error in chainparams.cpp

hashGenesisBlock = genesis.GetHash();
assert(hashGenesisBlock == uint256("0x12a765e31ffd4059bada1e25190f6e98c99d9714d334efa41a195a7e7e04bfe2"));

If I continue , I will get new error.

ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: ReadBlockFromDisk : Errors in block header
ERROR: VerifyDB() : *** ReadBlockFromDisk failed at 385772, hash=aaca90c78316879c0bd6f0200096f1c50e659d94a86eb8235b62f7f1133c5805