blockchain-foundry / gcoin-community Goto Github PK

採用multi-sig的方式來投票以及發license

支援blockchain中的資料遮蔽

1. Adjust the authority of Alliance; Add a new role Miner
   • Alliance
     • Remove the mining permission
   • MINER
     • Mining
   • Issuer
     • No difference
2. Genesis block structure adjustment
   • Add the alliance and miner information into genesis block
   • Alliance and miner information is provided by configuration file (gcoin.conf)

如題，reindex的時候那些cache裡的資料沒清，大部分檢查都會失敗

2個問題
1.
Build the GCoin 這個步驟做完，在make會出現錯誤

cd ~
git clone https://github.com/OpenNetworking/gcoin-community.git
cd ~/gcoin-community
./autogen.sh --without-gui --without-miniupnpc
make

Running 這個步驟bitcoin改gcoin

Place a configure file in ~/.bitcoin/bitcoin.conf with the following contents (you don't need to modify anything)

as title

as title

hi, i freshly installed the gcoin-community on my Ubuntu server 14.04 LTS

my gcoin.conf
root@GN:~# more ~/.gcoin/gcoin.conf rpcuser=username rpcpassword=password rpcport=6969 alliance=512102e00c5d4cd66ec85170747d0f7e457c4fe04eb1fafffcf8feb0862be7f14c99e75 1ae miner=1QAshXFAMvBLdbg5HLstsHBULn4WmNmjD

and after that:

root@GN:~# gcoin-cli getinfo { "version" : 1020101, "protocolversion" : 70002, "walletversion" : 60000, "blocks" : 0, "timeoffset" : 0, "connections" : 0, "proxy" : "", "difficulty" : 0.00024414, "testnet" : false, "keypoololdest" : 1507317525, "keystoresize" : 101, "errors" : "" }

what is wrong with that?
thanks for hints

Tom

rpc help 裡面好像有很多沒改

• fix cache problem
• fix rpc: sendlicense bug
• update unit test
• remove QT
• rename:
  • bitcoind -> gcoined
  • bitcoin-cli -> gcoin-cli
  • getasseetinfo -> getlicenseinfo
  • getlicenseinfo -> getlicenselist

shuwei@shuweiSony:$ bitcoind -gcoin -daemon
gCoin server starting
shuwei@shuweiSony:$ : Corrupted block database detected.

Do you want to rebuild the block database now?
y
y: command not found
shuwei@shuweiSony:~$

這個有空來修一下好了，這邊本來是qt的東西，看要拿掉還是要讓使用者輸入yes/no。

exchange應該藉由其他機制達成,
實作在blockchain protocol上並不適合

We now using getnewaddress to return a fixed address to recognize the node identity (used for Alliance). We need a new rpc to get the identity address, and change getnewaddress back to get the new addresses.

在auto-test中發生了此問題.

初步追蹤推測是blockfork時所造成的問題

有空來把它改成base58check
reson:

1. 現在太長
2. 沒有check (防呆)

目前在試用1.1版中，
關於指令中常出現的account，目前有一些疑問。

我先以getfixedaddress，查詢結果為1Cj2ij (address先以前6碼表示)

接著再setaccount 1Cj2ij Reki
但在getaccountaddress Reki
卻得到 176gaG

花時間找了一下後，發現listonewalletaddress的結果是 176gaG
而且getaccount 176gaG跟getaccount 1Cj2ij都是Reki
因為我從未用過'176gaG'，所以有些疑問
還請教目前gcoin account的定義為何？

p.s. 其他像getassetinfo等新指令，似乎尚無法使用？

Node在重啟時由於讀入cache的狀態和checkblock時的時間點會不一樣，加上由於無法紀錄在各個block height時當下的alliance狀態，可能造成重啟時dynamic difficulty check failure

Development process

Developers work in their own trees, then submit pull requests when they think their feature or bug fix is ready.

If it is a simple/trivial/non-controversial change, then one of the GCOIN development team members simply pulls it.

The patch will be accepted if there is broad consensus that it is a good thing. Developers should expect to rework and resubmit patches if the code doesn't match the project's coding conventions (see doc/coding.md) or are controversial.

permission structure調整過後,
各種type的maturity也應做相對應的調整.

• Remove the caching of block miner
• Error handling when the on-disk data is partially unreadable

RPC assignfixedaddress assigns an address that is in keypool, and removes it from the keypool after it is assigned to avoid it from being used by other purposes, ex. getnewaddress. However, this means that it cannot be assigned again if it is not in the keypool afterwards.

as tittle,

在新的permission架構下只允許3個address的multi-sig顯然不夠用

getlicenselist returns the license that is owned by the user only. Entire license list should be able to showed by rpc command.

bitcoin/bitcoin#3902

Dynamic difficulty failed when blockchain fork

A block's pow check may failed if it connect to fork-chain
It's due to cache of miner state.

目前checkpoint是hard code，我想是不是讓user手動增加一個checkpoint list 的file來檢查。
genesis block的check point還是可以寫死或是放進這個file。
方便我們sync blockchain，也方便私鏈檢查他們自己的blockchain。

Returns error: {"code":-1,"message":"ReserveKeyFromKeyPool() : read failed"}

As title, 看起來這件事被忽略掉了

bitcoin-tx
bitcoin test

return error: {"code":-5,"message":"No information available about transaction"}

Remove the unsupported document.

Seems that reservekey is no longer needed in CommitTransaction

Several RPCs and functions does not support multi-color query, ex. gettransaction

get ban when send confidential tx to node can't read.

連上140.112.29.201:12321之後，
getinfo 會出現以下警告訊息：「check your network connection, 66 blocks received in the last 4 hours (960 expected) at height 759」
但是網路應該其實沒有問題，可能可以修掉一些多餘的warnings

​jerry@jerry-VirtualBox:~/gcoin-community$ ./src/bitcoin-cli -gcoin getinfo
{ "version" : 1010000,
"protoc​​olversion" : 70002,
"walletversion" : 60000,
"blocks" : 759,
"timeoffset" : 0,
"connections" : 1,
"proxy" : "",
"difficulty" : 0.00388043,
"testnet" : false,
"keypoololdest" : 1461837034,
"keystoresize" : 1,
"errors" : "WARNING: check your network connection, 66 blocks received in the last 4 hours (960 expected) at height 759" }

While mining, running assignfixedaddress to change the default address to a non-miner address causes data loss.

這樣看起來應該比較正常吧，要求使用者要在下載軟體後，自己再另外下載 license 全文來看總是很奇怪的？

1. 沒有把接收到的orphan block標示為已收
2. 在每240個block作base難度調整時會因為orphan block沒處理好出錯

As title. LICENSE type transaction that transfers the existed license to another address cannot be applied when connecting block.

每次開server如果不加reindex，都會讀不到chain上的資料，
後來在bitcoin.conf裡加上txindex=1並加上reindex重開一次才解決問題

member only的機制應由其他方法實作