[Dev] Develop new core 0.9.3 for feathercoin, together
-
We need all our devs on this…
After the Neo fork, this should be the next thing we do in regards to forks. (I assume it requires a fork?)
But yeah, lets get our own core/ the btc core… finally cut all ties with ltc…
-
No, 0.9.3 core don’t need hard fork, but it will upgrade database. so you can not go back 0.8.6.2
-
this would basically mean u should have continuous support by yourself adding bitcoin updates to source
if there would be, then i would want to see ufo in same core version after feathercoin.
remember to have guys ready to compile static wallets to mac and linux… windows is the easy one
-
…remember to have guys ready to compile static wallets to mac and linux… windows is the easy one
I see it just the other way round: Linux is the easy one.
When a final version is released and Bushstar gives a go, I can create linux deb and rpm installation packages easily ;)
No Mac or tools for Mac available unfortunatelly
-
In this several days ,I had updated site information, I will continue tomorrow ^-^
-
I see it just the other way round: Linux is the easy one.
When a final version is released and Bushstar gives a go, I can create linux deb and rpm installation packages easily ;)
No Mac or tools for Mac available unfortunatelly
i just noticed ufo has no static linux wallet at its main post.
bushstar could like to add it…
-
I like add a page for merchant. When you click a merchant Logo , open it from feathercoin-core wallet.
-
I update menu,
1.Wallet menu
openAction
backupWalletAction
encryptWalletAction
changePassphraseAction
usedSendingAddressesAction
usedReceivingAddressesAction
2.Settings menu
signMessageAction
verifyMessageAction
openRPCConsoleAction
3.Advanced menu
accountReportAction
merchantListAction
4.Help menu
showHelpMessageAction
aboutAction
aboutQtAction
git push source code in https://github.com/cqtenq/feathercoin_core
Today ,had finished the job.
I will check ACP ,eHRC , qr-import ,neoscrypt and history fork for 0.9.3 core wallet tomorrow.
-
Develop core wallet for neoscrypt , I had finished it Today. Also I do history fork.
I can work normal.
-
Today, upgrade db-4.8.30.NC to db-5.1.29.NC. I like BerkeleyDB.5.1 :)
You need to add bitcoin_find_bdb51.m4 in src/m4
2014-10-23 14:47:48 Feathercoin version v0.9.3.0-git-Standard (Fri, 12 September 2014 16:29:30 -0400) 2014-10-23 14:47:48 Using OpenSSL version OpenSSL 1.0.1i 6 Aug 2014 2014-10-23 14:47:48 Using BerkeleyDB version Berkeley DB 5.1.29: (October 25, 2011) 2014-10-23 14:47:48 Default data directory C:\Users\lizhi.lizhi-PC\AppData\Roaming\Feathercoin 2014-10-23 14:47:48 Using data directory C:\Users\lizhi.lizhi-PC\AppData\Roaming\Feathercoin 2014-10-23 14:47:48 Using at most 125 connections (2048 file descriptors available) 2014-10-23 14:47:48 Using 2 threads for script verification 2014-10-23 14:47:48 Using wallet wallet.dat 2014-10-23 14:47:48 init message: Verifying wallet... 2014-10-23 14:47:48 CDBEnv::Open : LogDir=C:\Users\lizhi.lizhi-PC\AppData\Roaming\Feathercoin\database ErrorFile=C:\Users\lizhi.lizhi-PC\AppData\Roaming\Feathercoin\db.log 2014-10-23 14:47:48 Bound to [::]:9336 2014-10-23 14:47:48 Bound to 0.0.0.0:9336 2014-10-23 14:47:48 init message: Loading block index...
-
I had Implemented ACP , add checkpointsync.cpp and checkpointsync.h to project , It looks normal. :)
I check debug.log , It can synchronized checkpoint.
2014-10-26 10:27:18 Before: 1c009936 0000000000993600000000000000000000000000000000000000000000000000
2014-10-26 10:27:18 After: 1c008eff 00000000008eff33333333333333333333333333333333333333333333333333
2014-10-26 10:27:18 ConnectBlock hashPrevBlock=3661d21636c8001d4411d951319d14e68d8b17f6086ea8566379fb118c87308d
2014-10-26 10:27:18 ConnectBlock view.GetBestBlock()=3661d21636c8001d4411d951319d14e68d8b17f6086ea8566379fb118c87308d
2014-10-26 10:27:18 UpdateTip: new best=24b16d47e958635c2dd283f2fe7291273d60aed1368a4a9628661b6aade1f6c4 height=431618 log2_work=57.824336 tx=1502948 date=2014-10-26 10:14:11 progress=0.999976
2014-10-26 10:27:18 ProcessBlock: ACCEPTED2014-10-26 10:27:40 Opened LevelDB successfully
2014-10-26 10:27:45 LoadBlockIndexDB(): last block file = 3
2014-10-26 10:27:45 LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=115238, size=91879279, heights=316415…431623, time=2014-07-20…2014-10-26)
2014-10-26 10:27:45 LoadBlockIndexDB(): synchronized checkpoint 24b16d47e958635c2dd283f2fe7291273d60aed1368a4a9628661b6aade1f6c4
2014-10-26 10:27:45 LoadBlockIndexDB(): transaction index disabled
2014-10-26 10:27:45 LoadBlockIndexDB(): hashBestChain=acee96e699e484cfc9776139508f002c27e19c0d5b79af664cd10b4268f9d23f height=431623 date=2014-10-26 10:19:38 progress=0.999985
2014-10-26 10:27:45 init message: Verifying blocks…Because 0.8.7 ACP code have some problem in 0.9.3 core , I re-write SetBestChain in main.cpp. I think Peter Bushnell to check it .
I push my codes ti Github.
-
what is the benfit /difference between db-4.8.30.NC to db-5.1.29.NC.
some quick easy info to understand? -
This is working out really well!
I’m really keen to see how this turns out.
-
what is the benfit /difference between db-4.8.30.NC to db-5.1.29.NC.
some quick easy info to understand?This is just the version of the DB library that is being used. I can’t find anything specific on the changes but I’m guessing minimum is performance improvements and bug fixes. :)
-
0.9.3 core wallet had support neoscrypt ,It is very good.
I modify core.h
/* Calculates block proof-of-work hash using either NeoScrypt or Scrypt */ uint256 GetPoWHash() const { unsigned int profile = 0x0; uint256 hash; neoscrypt((unsigned char *) &nVersion, (unsigned char *) &hash, profile); return(hash); }
0.9.3 core sync blockchain normal .
Debug.log
2014-10-27 07:23:10 nTargetTimespan = 60 nActualTimespan = 58 2014-10-27 07:23:10 Before: 1c49674a 0000000049674a00000000000000000000000000000000000000000000000000 2014-10-27 07:23:10 After: 1c46f4e9 0000000046f4e9aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa 2014-10-27 07:23:10 ConnectBlock hashPrevBlock=b933f9d19bc60265e008fad2dd8c9f1c9829d19928d1ae8c9f67d5a816eb30cf 2014-10-27 07:23:10 ConnectBlock view.GetBestBlock()=b933f9d19bc60265e008fad2dd8c9f1c9829d19928d1ae8c9f67d5a816eb30cf 2014-10-27 07:23:10 UpdateTip: new best=e61b145c955ea2a0b36ec5985388acffe0a207d0fa7e7ae41c14ab7f568bc086 height=432727 log2_work=57.827305 tx=1504547 date=2014-10-27 06:21:27 progress=0.999886 2014-10-27 07:23:10 ProcessBlock: ACCEPTED
I can send feathercoin to 0.8.7 from 0.9.3 core ,or to 0.9.3 core from 0.8.7. :)
-
Enhancement note : Transaction details
Just noticed (again) so making note. The Transaction details in transactions TAB are quite limited, is there any other details available e.g. the block number, better format?
Status: 19 confirmations
Date: 28/10/2014 11:37
Source: Generated
Credit: 0.22871001 FTC (matures in 82 more blocks)
Net amount: 0.00 FTC
Transaction ID: 76ba496b293aa595fa74c4e0cf79b48f236717430f93132259ff5563f658b3f9 -
Absolut awesome work Lizhi!!
-
I have almost finished it, but I’m stuck on this last question. Genesis block is unacceptable. If you upgrade from 0.8.X ,it is all right. But if you are new user, The core can not install normal. :-
Debug:
2014-10-31 15:15:34 Initializing databases…
2014-10-31 15:15:34 Pre-allocating up to position 0x1000000 in blk00000.dat
2014-10-31 15:15:34 ERROR: amount CheckProofOfWork() : hash doesn’t match nBits
2014-10-31 15:15:34 ERROR: Check the header ReadBlockFromDisk : Errors in block header
2014-10-31 15:15:34 *** Failed to read block
2014-10-31 15:15:36 ERROR: LoadBlockIndex() : genesis block not accepted
2014-10-31 15:15:36 Aborted block database rebuild. Exiting. -
Luckily, I found a way to solve the problem. I write CheckProofOfWork in CBlockHeader class, When nHeight>=nForkFour ,use neoscrypt, When nHeight
-
I add my site to DNS, After users install core wallet, have 2 address can work
vSeeds.push_back(CDNSSeedData(“ftc-c.com”, “www.ftc-c.com”));
vSeeds.push_back(CDNSSeedData(“pool.ftc-c.com”, “pool.ftc-c.com”));They are written to peers.dat :)****
I think I’m finished development. I will test multi-sign.