好,我们接着上一章,第五十五章无法发布,参考第三十八章浏览方法。就是该分类栏简介里的说明。
原先是运行b节点的代码,然后再运行a节点代码
1.思路
现在这里我改了一下,为了更好的配合。
先运行a节点代码,然后马上运行b节点代码,a节点加上一个延时5秒,等待两节点连接上,再发送交易,a节点关键代码如下:
cpp
Init2();
Sleep(5000);
SendMoney1();//转账,发起一笔tx
然后b节点,把这两句注释就行了:
cpp
//Sleep(5000);
//SendMoney1();//转账,发起一笔tx
2.更改方案
这样的测试不行,时间很难控制,因为BitcoinMiner我只设置了挖矿一次,否则以这个速度会大量产生区块。所以程序只能执行一次。
我再启动b节点后,b节点还没等到交易过来,就自己挖了一个矿,只有coinbase交易,然后后面的工作对接不上了。
现在的情况是,a节点6个区块,b节点现在产生第7个区块了。
我们先双方取消交易,取消挖矿,然后运行两个节点,再同步一次,同步到第7个区块。
然后我们手动指定第8个区块的难度。就是通过判断高度,在GetNextWorkRequired判断只要是第8个区块,则直接返回0x1e00ffff。
我们先来同步一下吧,先把b节点的第7个区块同步过来(注意双方都不要挖矿,注释掉语句)
a节点输出信息:
cpp
sending: version (46 bytes)
dbenv.open strAppDir=c:\test\btc
mapAddresses:
-----
LoadBlockIndex(): hashBestChain=00000eca18a942 height=5
fGenerateBitcoins = 0
nTransactionFee = 0
addrLocalHost = 192.168.2.101:8333
bound to addrLocalHost = 192.168.2.101:8333
ThreadSocketHandler started
ThreadMessageHandler started
ThreadOpenConnections started
RandAddSeed() got 120 bytes of performance data
accepted connection from 192.168.2.106:51619
sending: version (46 bytes)
ProcessMessages(66 bytes)
received: version (46 bytes) 71 11 01 00 01 00 00 00 00 00 00 00 76 74 fa 6a 00 00 00 00 01 00 00 00 00
Added time data, samples 2, ip 6a02a8c0, offset +0 (+0 minutes)
sending: getblocks (261 bytes)
version addrMe = 192.168.2.101:8333
ProcessMessages(313 bytes)
received: getblocks (293 bytes) 71 11 01 00 08 75 89 b2 ec 19 00 e6 59 88 b0 60 c5 ef 9d 81 ed 87 c3 68 9b
getblocks -1 to 00000000000000
ProcessMessages(57 bytes)
received: inv (37 bytes) 01 02 00 00 00 75 89 b2 ec 19 00 e6 59 88 b0 60 c5 ef 9d 81 ed 87 c3 68 9b
got inventory: block 0000047929a45f new
askfor block 0000047929a45f 0
sending getdata: block 0000047929a45f
sending: getdata (37 bytes)
ProcessMessages(235 bytes)
received: block (215 bytes) 00 00 00 00 e5 c9 aa ca e7 6e 5e f8 55 bd 88 f5 c5 86 43 64 fc af db 62 60
received block:
CBlock(hash=0000047929a45f, ver=0, hashPrevBlock=00000eca18a942, hashMerkleRoot=5347b7, nTime=1794797196, nBits=1f000fff, nNonce=284023, vtx=1)
CTransaction(hash=5347b7, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(000000, -1), coinbase 04ff0f001f0101)
CTxOut(nValue=50.00000000, scriptPubKey=0xACB720F407DF7D8E7A6F70)
vMerkleTree:
AddToBlockIndex: new best=0000047929a45f height=6
ProcessBlock: ACCEPTED
同步成功,可以看到a节点现在高度为6,现在双方都有7个区块了。
3.GetNextWorkRequired
直接在GetNextWorkRequired函数开头加上这句:
cpp
if ((pindexLast->nHeight + 1) == 7)
return 0x1e00ffff;
位置:
cpp
unsigned int GetNextWorkRequired(const CBlockIndex* pindexLast)
{
const unsigned int nTargetTimespan = 14 * 24 * 60 * 60; // two weeks
const unsigned int nTargetSpacing = 10 * 60;
const unsigned int nInterval = nTargetTimespan / nTargetSpacing;
//临时指定 手动调整难度
if ((pindexLast->nHeight + 1) == 7)
return 0x1e00ffff;
// Genesis block
if (pindexLast == NULL)
return bnProofOfWorkLimit.GetCompact();
// Only change once per interval
if ((pindexLast->nHeight + 1) % nInterval != 0)
return pindexLast->nBits;
// Go back by what we want to be 14 days worth of blocks
const CBlockIndex* pindexFirst = pindexLast;
for (int i = 0; pindexFirst && i < nInterval - 1; i++)
pindexFirst = pindexFirst->pprev;
assert(pindexFirst);
这样就指定了,第8个区块,就是高度为7的区块,难度是0x1e00ffff;
4.思考影响
如果以后这里的代码不改,是没有问题的。但我想的是第8个区块上链后,我再把这个指定删除掉。会不会有问题呢?首先,第一个问题是,如果是有第三个节点,进行同步的话,那肯定是出错的。
它会验证的。但是如果我只有两个节点呢?不打算测试第三个节点呢。意思是区块加载的时候以及其它方面,比如下一个区块产生的时候,会去验证第8个区块的难度是正常生成的吗?还是直接引用的第8个难度,然后再根据情况是否调用,就是会走:
cpp
// Store to disk
if (!pblock->AcceptBlock())
这个验证一样的链条吗,我们需要结合代码实际去看。这里留个研究点。
我们先来产生第8个区块。
测试代码,不改,就是那个a节点开头,延迟5秒的设定。
5.第二次错误
先运行a节点,再运行b节点。
这里还是有个逻辑问题,我们需要设置一下,首先a节点,没问题。虽然现在b节点,不会快速出块了,但它依然会挖自己的区块,因为一启动他就挖矿,他还没接到交易。等他接到交易时,已经在挖矿了。当然现在有这么多问题,只是因为我们没实现链重组功能。否则无所谓什么先后,以及时间控制。随时随地启动都行,最后总会同步重组产生唯一最优链,不怕有分叉。
现在这个错误发生了,我马上关闭了,因为难度设置原因。两个节点都没有出块。
现在的情况是,第8个区块没产生,但是a节点的交易已经进了钱包了。
如果再启动a节点的话,就会调用:ReacceptWalletTransactions函数,把钱包的这笔交易重新添加到交易池。
但是没有广播了。
我们来看一下,其他地方会不会广播这笔tx,有一个地方方,就是新区块产生时,会调用:
就是新区块产生时:
cpp
RelayWalletTransactions()
但是这个的目的是为了把剩下的未确认的交易广播一下,因为新区块产生了,还看看有的没有上块,就广播出去。
所以这里的广播对于我们没用,你a节点,都产生第8个区块了。那里面还有那条tx交易吗。
6.重新广播
这样,我看了一下代码,我们可以手动调用RelayWalletTransactions函数,广播钱包中未确认的交易。
我们需要修复一下这个函数的代码:
cpp
void RelayWalletTransactions()
{
static int64 nLastTime;
if (GetTime() - nLastTime < 10 * 60)
return;
nLastTime = GetTime();
// Rebroadcast any of our txes that aren't in a block yet
printf("RelayWalletTransactions()\n");
CTxDB txdb("r");
CRITICAL_BLOCK(cs_mapWallet)
{
// Sort them in chronological order
multimap<unsigned int, CWalletTx*> mapSorted;
for(PAIRTYPE(const uint256, CWalletTx) & item: mapWallet)
{
CWalletTx& wtx = item.second;
mapSorted.insert(make_pair(wtx.nTimeReceived, &wtx));
}
for(PAIRTYPE(const unsigned int, CWalletTx*) & item:mapSorted)
{
CWalletTx& wtx = *item.second;
wtx.RelayWalletTransaction(txdb);
}
}
}
他会遍历钱包中的tx,然后调用 wtx.RelayWalletTransaction(txdb);这个函数内部会做是否上链的判断,如果是未确认交易,则重新广播。
好,我们在a节点代码中这样调用:
cpp
void Init2()
{
LoadAddresses(); //加载地址库--mapAddresses
LoadBlockIndex(); //加载区块索引--mapBlockIndex等
LoadWallet(); //加载钱包账号 tx--mapPubKeys、mapWallet等
ReacceptWalletTransactions();//将钱包未确认交易重新加入池子
RelayWalletTransactions();// 重新广播
StartNode();//启动网络节点
}
然后取消掉a节点的SendMoney1操作,因为我们已经有了一笔交易,当然写上也没事。
那样区块会有三笔交易,我们需要数量尽量少,这样好观察一些。
也就是说,如果挖矿,a,b节点,都显示,两笔tx正在挖矿中(一笔是coinbase),那么就没问题了。
好,现在我们还要改b节点的代码,就是为了避免之前的错误。
我们在b节点调用BitcoinMiner函数之前,直接延迟20秒,以保证,接到tx后再挖矿。
好,再次启动节点,我们需要先启动b节点,这样当a节点广播的时候,b节点能保证收到。
否则广播一次,b节点还未启动。那就错过这次广播机会了。
7.第三次出错
还是出错了,6个0的难度出块速度依然很快,在b节点,还未挖矿前,a节点就已经出块。
我们来看一下双方的输出信息,看后续怎么协调:
a节点:
cpp
sending: version (46 bytes)
dbenv.open strAppDir=c:\test\btc
mapAddresses:
-----
LoadBlockIndex(): hashBestChain=0000047929a45f height=6
fGenerateBitcoins = 0
nTransactionFee = 0
AcceptTransaction(): accepted eb135c
RelayWalletTransactions()
Relaying wtx eb135c
addrLocalHost = 192.168.2.101:8333
bound to addrLocalHost = 192.168.2.101:8333
ThreadOpenConnections started
ThreadMessageHandler started
ThreadSocketHandler started
RandAddSeed() got 120 bytes of performance data
accepted connection from 192.168.2.106:60831
sending: version (46 bytes)
ProcessMessages(379 bytes)
received: version (46 bytes) 71 11 01 00 01 00 00 00 00 00 00 00 93 81 fa 6a 00 00 00 00 01 00 00 00 00
Added time data, samples 2, ip 6a02a8c0, offset -1 (+0 minutes)
sending: getblocks (293 bytes)
version addrMe = 192.168.2.101:8333
received: getblocks (293 bytes) 71 11 01 00 08 75 89 b2 ec 19 00 e6 59 88 b0 60 c5 ef 9d 81 ed 87 c3 68 9b
getblocks -1 to 00000000000000
BitcoinMiner started
Running BitcoinMiner with 2 transactions in block
BitcoinMiner:
proof-of-work found
hash: 000000909f4d8076d5b54a5151ea543cc564c4ee73e730f4b5d4337a2c657659
target: 000000ffff000000000000000000000000000000000000000000000000000000
CBlock(hash=000000909f4d80, ver=0, hashPrevBlock=0000047929a45f, hashMerkleRoot=9fa157, nTime=1794802070, nBits=1e00ffff, nNonce=241168, vtx=2)
CTransaction(hash=948868, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(000000, -1), coinbase 04ffff001e0101)
CTxOut(nValue=50.00000000, scriptPubKey=0xF01FEF57BBA09711119EEE)
CTransaction(hash=eb135c, ver=1, vin.size=1, vout.size=2, nLockTime=0)
CTxIn(COutPoint(7a9164, 1), scriptSig=0x01BF59AD643793C911E44D)
CTxOut(nValue=5.00000000, scriptPubKey=OP_DUP OP_HASH160 0x188F)
CTxOut(nValue=25.00000000, scriptPubKey=0x0FECEB8007FEA4D2D6F523)
vMerkleTree: 948868 eb135c 9fa157
AddToWallet 948868 new
AddToWallet eb135c update
AddToBlockIndex: new best=000000909f4d80 height=7
ProcessBlock: ACCEPTED
sending: inv (37 bytes)
ProcessMessages(57 bytes)
received: getdata (37 bytes) 01 02 00 00 00 59 76 65 2c 7a 33 d4 b5 f4 30 e7 73 ee c4 64 c5 3c 54 ea 51
received getdata for: block 000000909f4d80
sending: block (449 bytes)
ProcessMessages(57 bytes)
received: inv (37 bytes) 01 02 00 00 00 25 ae 3b d8 2c c7 5b 18 11 bc e2 84 b2 c3 fd e8 36 40 74 81
got inventory: block 0000006e86fb7f new
askfor block 0000006e86fb7f 0
sending getdata: block 0000006e86fb7f
sending: getdata (37 bytes)
ProcessMessages(235 bytes)
received: block (215 bytes) 00 00 00 00 59 76 65 2c 7a 33 d4 b5 f4 30 e7 73 ee c4 64 c5 3c 54 ea 51 51
received block:
CBlock(hash=0000006e86fb7f, ver=0, hashPrevBlock=000000909f4d80, hashMerkleRoot=49a8d1, nTime=1794802082, nBits=1e00ffff, nNonce=436388, vtx=1)
CTransaction(hash=49a8d1, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(000000, -1), coinbase 04ffff001e0101)
CTxOut(nValue=50.00000000, scriptPubKey=0x219B4E0EAC453046BFDCBF)
vMerkleTree:
AddToBlockIndex: new best=0000006e86fb7f height=8
ProcessBlock: ACCEPTED
b节点:
cpp
sending: version (46 bytes)
dbenv.open strAppDir=c:\test\btc
mapAddresses:
CAddress(192.168.2.101:8333)
-----
LoadBlockIndex(): hashBestChain=0000047929a45f height=6
fGenerateBitcoins = 0
nTransactionFee = 0
addrLocalHost = 192.168.2.106:8333
bound to addrLocalHost = 192.168.2.106:8333
ThreadMessageHandler started
ThreadSocketHandler started
ThreadOpenConnections started
RandAddSeed() got 120 bytes of performance data
trying 192.168.2.101:8333
connected 192.168.2.101:8333
sending: version (46 bytes)
ProcessMessages(66 bytes)
received: version (46 bytes) 71 11 01 00 01 00 00 00 00 00 00 00 94 81 fa 6a 00 00 00 00 00 00 00 00 00
Added time data, samples 2, ip 6502a8c0, offset +0 (+0 minutes)
sending: getblocks (293 bytes)
version addrMe = 192.168.2.106:60831
ProcessMessages(313 bytes)
received: getblocks (293 bytes) 71 11 01 00 08 75 89 b2 ec 19 00 e6 59 88 b0 60 c5 ef 9d 81 ed 87 c3 68 9b
getblocks -1 to 00000000000000
ProcessMessages(57 bytes)
received: inv (37 bytes) 01 02 00 00 00 59 76 65 2c 7a 33 d4 b5 f4 30 e7 73 ee c4 64 c5 3c 54 ea 51
got inventory: block 000000909f4d80 new
askfor block 000000909f4d80 0
sending getdata: block 000000909f4d80
sending: getdata (37 bytes)
ProcessMessages(469 bytes)
received: block (449 bytes) 00 00 00 00 75 89 b2 ec 19 00 e6 59 88 b0 60 c5 ef 9d 81 ed 87 c3 68 9b 87
received block:
CBlock(hash=000000909f4d80, ver=0, hashPrevBlock=0000047929a45f, hashMerkleRoot=9fa157, nTime=1794802070, nBits=1e00ffff, nNonce=241168, vtx=2)
CTransaction(hash=948868, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(000000, -1), coinbase 04ffff001e0101)
CTxOut(nValue=50.00000000, scriptPubKey=0xF01FEF57BBA09711119EEE)
CTransaction(hash=eb135c, ver=1, vin.size=1, vout.size=2, nLockTime=0)
CTxIn(COutPoint(7a9164, 1), scriptSig=0x01BF59AD643793C911E44D)
CTxOut(nValue=5.00000000, scriptPubKey=OP_DUP OP_HASH160 0x188F)
CTxOut(nValue=25.00000000, scriptPubKey=0x0FECEB8007FEA4D2D6F523)
vMerkleTree:
AddToBlockIndex: new best=000000909f4d80 height=7
ProcessBlock: ACCEPTED
BitcoinMiner started
Running BitcoinMiner with 1 transactions in block
BitcoinMiner:
proof-of-work found
hash: 0000006e86fb7f48310f0a3f81744036e8fdc3b284e2bc11185bc72cd83bae25
target: 000000ffff000000000000000000000000000000000000000000000000000000
CBlock(hash=0000006e86fb7f, ver=0, hashPrevBlock=000000909f4d80, hashMerkleRoot=49a8d1, nTime=1794802082, nBits=1e00ffff, nNonce=436388, vtx=1)
CTransaction(hash=49a8d1, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(000000, -1), coinbase 04ffff001e0101)
CTxOut(nValue=50.00000000, scriptPubKey=0x219B4E0EAC453046BFDCBF)
vMerkleTree: 49a8d1
AddToWallet 49a8d1 new
AddToBlockIndex: new best=0000006e86fb7f height=8
ProcessBlock: ACCEPTED
sending: inv (37 bytes)
ProcessMessages(57 bytes)
received: getdata (37 bytes) 01 02 00 00 00 25 ae 3b d8 2c c7 5b 18 11 bc e2 84 b2 c3 fd e8 36 40 74 81
received getdata for: block 0000006e86fb7f
sending: block (215 bytes)
RandAddSeed() got 120 bytes of performance data
我们先分析一下代码吧,这里有一个问题要解决,那就是:
cpp
RelayWalletTransactions();// 重新广播
b节点好像没收到tx inv消息,反而是a节点先挖出来的那个区块先收到了。
目前先把这个问题解决。两个节点的协调的问题,已经想好解决方法了,其实是我思路有问题。
不应该用延时的这种不好控制,全靠估计的方法。
我们直接,输入字符控制,按回车键下一步。等他们都连接好,然后也都有那笔tx,然后再按回车键,同时挖矿。通过命令行接收输入来阻塞当前代码。
8.理清第三次过程
我们先要整理,看当前a,b节点的区块情况,根据输出的信息。
a节点先是挖出一个块,就是高度为7,然后广播给b节点。由于b节点设置了延迟,此时还没开始挖块,这样这个块同步好了,也成为b节点的最优链,接着b节点,开始挖矿,用的父区块哈希是高度7的哈希,挖出来后,高度8的区块广播给a,a同步好后ok。
此时,虽然两个节点产生了不同的区块,但没有产生分叉,是接力式产生的。
所以我们不用再协调了。从这里的区块同步也可以看出来,挖块然后广播再同步这些功能没问题。
9.测试交易广播
主要的问题是广播tx,为什么b节点没看到信息,应该是没收到。
我们来单独测试一下,为了避免产生实际的区块,现在a,b节点都取消挖矿。
只是测试一下广播交易,a节点代码如下:
cpp
int main()
{
Init2();
cin.get();
SendMoney1();//转账,发起一笔tx
}
(后注:上面代码不完全,因为中间隔着一大堆注释,所以我只展示关键代码,就是少了这个:
cpp
while (true)
{
Sleep(1000 * 60);
}
多线程,程序会提前退出,以后有这个问题,参考这个说明)
b节点只要不挖矿就行,等待广播的tx。
我们先运行a节点,再运行b节点。连接上后,就在a节点的控制台,按一下回车键就可发起一笔交易。
a节点输出信息:
cpp
sending: version (46 bytes)
dbenv.open strAppDir=c:\test\btc
mapAddresses:
-----
LoadBlockIndex(): hashBestChain=0000006e86fb7f height=8
fGenerateBitcoins = 0
nTransactionFee = 0
RelayWalletTransactions()
addrLocalHost = 192.168.2.101:8333
bound to addrLocalHost = 192.168.2.101:8333
ThreadOpenConnections started
ThreadMessageHandler started
ThreadSocketHandler started
RandAddSeed() got 120 bytes of performance data
accepted connection from 192.168.2.106:61765
sending: version (46 bytes)
ProcessMessages(66 bytes)
received: version (46 bytes) 71 11 01 00 01 00 00 00 00 00 00 00 9e 8e fa 6a 00 00 00 00 01 00 00 00 00
Added time data, samples 2, ip 6a02a8c0, offset +0 (+0 minutes)
sending: getblocks (357 bytes)
version addrMe = 192.168.2.101:8333
ProcessMessages(377 bytes)
received: getblocks (357 bytes) 71 11 01 00 0a 25 ae 3b d8 2c c7 5b 18 11 bc e2 84 b2 c3 fd e8 36 40 74 81
getblocks -1 to 00000000000000
//此为回车键后的输出信息
AddToWallet 4a26fe new
SendMoney: 4a26fe
AcceptTransaction(): accepted 4a26fe
Relaying wtx 4a26fe
sending: inv (37 bytes)
ProcessMessages(57 bytes)
received: getdata (37 bytes) 01 01 00 00 00 0c 77 f3 2a 94 c6 3c 86 10 7b a9 1a f2 64 01 00 a0 a6 8b fd
received getdata for: tx 4a26fe3e9fe8ed
sending: tx (233 bytes)
b节点:
cpp
sending: version (46 bytes)
dbenv.open strAppDir=c:\test\btc
mapAddresses:
CAddress(192.168.2.101:8333)
-----
LoadBlockIndex(): hashBestChain=0000006e86fb7f height=8
fGenerateBitcoins = 0
nTransactionFee = 0
addrLocalHost = 192.168.2.106:8333
bound to addrLocalHost = 192.168.2.106:8333
ThreadMessageHandler started
ThreadOpenConnections started
ThreadSocketHandler started
RandAddSeed() got 120 bytes of performance data
trying 192.168.2.101:8333
connected 192.168.2.101:8333
sending: version (46 bytes)
ProcessMessages(66 bytes)
received: version (46 bytes) 71 11 01 00 01 00 00 00 00 00 00 00 9e 8e fa 6a 00 00 00 00 00 00 00 00 00
Added time data, samples 2, ip 6502a8c0, offset +0 (+0 minutes)
sending: getblocks (357 bytes)
version addrMe = 192.168.2.106:61765
ProcessMessages(377 bytes)
received: getblocks (357 bytes) 71 11 01 00 0a 25 ae 3b d8 2c c7 5b 18 11 bc e2 84 b2 c3 fd e8 36 40 74 81
getblocks -1 to 00000000000000
//a节点回车后 b节点的输出信息
ProcessMessages(57 bytes)
received: inv (37 bytes) 01 01 00 00 00 0c 77 f3 2a 94 c6 3c 86 10 7b a9 1a f2 64 01 00 a0 a6 8b fd
got inventory: tx 4a26fe3e9fe8ed new
askfor tx 4a26fe3e9fe8ed 0
sending getdata: tx 4a26fe3e9fe8ed
sending: getdata (37 bytes)
ProcessMessages(253 bytes)
received: tx (233 bytes) 01 00 00 00 01 ab 67 ab 39 4a d7 6f b3 e2 97 83 2e e9 47 1f 7b 91 ea 40 0a
AcceptTransaction(): accepted 4a26fe
从这里看到,广播tx也是没问题,那么我可以得出来结论,广播tx,然后同时挖矿,再广播区块,然后同步。这些功能没问题。只是我们用延时这种测试方法,导致无法很好的产生测试环境。
用cin.get()来控制,即可解决。
现在我们需要解决另外一些问题,先不急着这样测试。
广播tx没问题,那有可能是:
cpp
RelayWalletTransactions();// 重新广播
这个没正常工作,我们再来测试一下。
我们注释a节点的这段代码:
cpp
//cin.get();
//SendMoney1();//转账,发起一笔tx
因为a节点之前创建的交易没有挖矿,所以钱包里正好有一笔未确认交易,配合我们的 RelayWalletTransactions()节点调用。
这里我们要先启动b节点,然后...等等,到这里我想我已经发现问题了:
cpp
RelayWalletTransactions();// 重新广播
StartNode();//启动网络节点
看到调用顺序了吗?节点都还没启动,给谁广播呢?
所以我们这样放:
cpp
StartNode();//启动网络节点
RelayWalletTransactions();// 重新广播
然后等b节点连接上,但是也不行。StartNode后,b节点可以连接了。
但是这里是同步执行的。所以最终是这样调用:
cpp
int main()
{
Init2();
cin.get();
RelayWalletTransactions();// 重新广播
//SendMoney1();//转账,发起一笔tx
//fGenerateBitcoins = 1;
//BitcoinMiner(); //挖矿 上链
while (true)
{
Sleep(1000 * 60);
}
}
等,a,b节点都连接上了,然后我们a节点回车,重新广播。
结果没有问题,b节点收到了这条tx。输出信息就不帖了。
10.再次测试
好,这次我们取消注释,a节点这样:
cpp
int main()
{
Init2();
cin.get();
RelayWalletTransactions();// 重新广播
//SendMoney1();//转账,发起一笔tx
cin.get();
fGenerateBitcoins = 1;
BitcoinMiner(); //挖矿 上链
while (true)
{
Sleep(1000 * 60);
}
}
b节点这样:
cpp
int main()
{
Init2();
cin.get();
//RelayWalletTransactions();// 重新广播
//SendMoney1();//转账,发起一笔tx
fGenerateBitcoins = 1;
BitcoinMiner(); //挖矿 上链
while (true)
{
Sleep(1000 * 60);
}
}
操作过程是:等他们连接上后,在a节点窗口按回车键,广播一笔tx。等待一会儿后。交易同步好,再同时按回车键,一起进行挖矿。
好,即将产生高度为9,第10个区块:
a节点输出信息:
cpp
sending: version (46 bytes)
dbenv.open strAppDir=c:\test\btc
mapAddresses:
-----
LoadBlockIndex(): hashBestChain=0000006e86fb7f height=8
fGenerateBitcoins = 0
nTransactionFee = 0
AcceptTransaction(): accepted 4a26fe
addrLocalHost = 192.168.2.101:8333
bound to addrLocalHost = 192.168.2.101:8333
ThreadOpenConnections started
ThreadMessageHandler started
ThreadSocketHandler started
RandAddSeed() got 120 bytes of performance data
accepted connection from 192.168.2.106:58883
sending: version (46 bytes)
ProcessMessages(66 bytes)
received: version (46 bytes) 71 11 01 00 01 00 00 00 00 00 00 00 14 95 fa 6a 00 00 00 00 01 00 00 00 00
Added time data, samples 2, ip 6a02a8c0, offset -1 (+0 minutes)
sending: getblocks (357 bytes)
version addrMe = 192.168.2.101:8333
ProcessMessages(377 bytes)
received: getblocks (357 bytes) 71 11 01 00 0a 25 ae 3b d8 2c c7 5b 18 11 bc e2 84 b2 c3 fd e8 36 40 74 81
getblocks -1 to 00000000000000
RelayWalletTransactions()
Relaying wtx 4a26fe
sending: inv (37 bytes)
ProcessMessages(57 bytes)
received: getdata (37 bytes) 01 01 00 00 00 0c 77 f3 2a 94 c6 3c 86 10 7b a9 1a f2 64 01 00 a0 a6 8b fd
received getdata for: tx 4a26fe3e9fe8ed
sending: tx (233 bytes)
BitcoinMiner started
Running BitcoinMiner with 2 transactions in block
BitcoinMiner:
proof-of-work found
hash: 0000001aadb3ceeadf6edc1c496c54e2ba2e8159e6c2df6485c1e64601bffd49
target: 000000ffff000000000000000000000000000000000000000000000000000000
CBlock(hash=0000001aadb3ce, ver=0, hashPrevBlock=0000006e86fb7f, hashMerkleRoot=0058cd, nTime=1794807082, nBits=1e00ffff, nNonce=670732, vtx=2)
CTransaction(hash=e0f399, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(000000, -1), coinbase 04ffff001e0101)
CTxOut(nValue=50.00000000, scriptPubKey=0xAC4467DD793BF2A999533A)
CTransaction(hash=4a26fe, ver=1, vin.size=1, vout.size=2, nLockTime=0)
CTxIn(COutPoint(eb135c, 1), scriptSig=0x01B33BEE08386D11680C8F)
CTxOut(nValue=5.00000000, scriptPubKey=OP_DUP OP_HASH160 0x188F)
CTxOut(nValue=20.00000000, scriptPubKey=0x0FECEB8007FEA4D2D6F523)
vMerkleTree: e0f399 4a26fe 0058cd
AddToWallet e0f399 new
AddToWallet 4a26fe update
AddToBlockIndex: new best=0000001aadb3ce height=9
ProcessBlock: ACCEPTED
sending: inv (37 bytes)
ProcessMessages(57 bytes)
received: getdata (37 bytes) 01 02 00 00 00 49 fd bf 01 46 e6 c1 85 64 df c2 e6 59 81 2e ba e2 54 6c 49
received getdata for: block 0000001aadb3ce
sending: block (448 bytes)
ProcessMessages(57 bytes)
received: inv (37 bytes) 01 02 00 00 00 b7 24 5f 78 98 77 aa f3 81 4c 54 65 e6 58 ce e4 3a bf 94 41
got inventory: block 00000040dc940b new
askfor block 00000040dc940b 0
sending getdata: block 00000040dc940b
sending: getdata (37 bytes)
ProcessMessages(235 bytes)
received: block (215 bytes) 00 00 00 00 49 fd bf 01 46 e6 c1 85 64 df c2 e6 59 81 2e ba e2 54 6c 49 1c
received block:
CBlock(hash=00000040dc940b, ver=0, hashPrevBlock=0000001aadb3ce, hashMerkleRoot=0e3474, nTime=1794807167, nBits=1e00ffff, nNonce=6066310, vtx=1)
CTransaction(hash=0e3474, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(000000, -1), coinbase 04ffff001e0102)
CTxOut(nValue=50.00000000, scriptPubKey=0x2FE48DB5E385E3D7F3AD2D)
vMerkleTree:
AddToBlockIndex: new best=00000040dc940b height=10
ProcessBlock: ACCEPTED
b节点输出信息:
cpp
sending: version (46 bytes)
dbenv.open strAppDir=c:\test\btc
mapAddresses:
CAddress(192.168.2.101:8333)
-----
LoadBlockIndex(): hashBestChain=0000006e86fb7f height=8
fGenerateBitcoins = 0
nTransactionFee = 0
addrLocalHost = 192.168.2.106:8333
bound to addrLocalHost = 192.168.2.106:8333
ThreadSocketHandler started
ThreadOpenConnections started
ThreadMessageHandler started
RandAddSeed() got 120 bytes of performance data
trying 192.168.2.101:8333
connected 192.168.2.101:8333
sending: version (46 bytes)
ProcessMessages(66 bytes)
received: version (46 bytes) 71 11 01 00 01 00 00 00 00 00 00 00 14 95 fa 6a 00 00 00 00 00 00 00 00 00
Added time data, samples 2, ip 6502a8c0, offset +0 (+0 minutes)
sending: getblocks (357 bytes)
version addrMe = 192.168.2.106:58883
ProcessMessages(377 bytes)
received: getblocks (357 bytes) 71 11 01 00 0a 25 ae 3b d8 2c c7 5b 18 11 bc e2 84 b2 c3 fd e8 36 40 74 81
getblocks -1 to 00000000000000
ProcessMessages(57 bytes)
received: inv (37 bytes) 01 01 00 00 00 0c 77 f3 2a 94 c6 3c 86 10 7b a9 1a f2 64 01 00 a0 a6 8b fd
got inventory: tx 4a26fe3e9fe8ed new
askfor tx 4a26fe3e9fe8ed 0
sending getdata: tx 4a26fe3e9fe8ed
sending: getdata (37 bytes)
ProcessMessages(253 bytes)
received: tx (233 bytes) 01 00 00 00 01 ab 67 ab 39 4a d7 6f b3 e2 97 83 2e e9 47 1f 7b 91 ea 40 0a
AcceptTransaction(): accepted 4a26fe
BitcoinMiner started
Running BitcoinMiner with 2 transactions in block
ProcessMessages(57 bytes)
received: inv (37 bytes) 01 02 00 00 00 49 fd bf 01 46 e6 c1 85 64 df c2 e6 59 81 2e ba e2 54 6c 49
got inventory: block 0000001aadb3ce new
askfor block 0000001aadb3ce 0
sending getdata: block 0000001aadb3ce
sending: getdata (37 bytes)
ProcessMessages(468 bytes)
received: block (448 bytes) 00 00 00 00 25 ae 3b d8 2c c7 5b 18 11 bc e2 84 b2 c3 fd e8 36 40 74 81 3f
received block:
CBlock(hash=0000001aadb3ce, ver=0, hashPrevBlock=0000006e86fb7f, hashMerkleRoot=0058cd, nTime=1794807082, nBits=1e00ffff, nNonce=670732, vtx=2)
CTransaction(hash=e0f399, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(000000, -1), coinbase 04ffff001e0101)
CTxOut(nValue=50.00000000, scriptPubKey=0xAC4467DD793BF2A999533A)
CTransaction(hash=4a26fe, ver=1, vin.size=1, vout.size=2, nLockTime=0)
CTxIn(COutPoint(eb135c, 1), scriptSig=0x01B33BEE08386D11680C8F)
CTxOut(nValue=5.00000000, scriptPubKey=OP_DUP OP_HASH160 0x188F)
CTxOut(nValue=20.00000000, scriptPubKey=0x0FECEB8007FEA4D2D6F523)
vMerkleTree:
AddToBlockIndex: new best=0000001aadb3ce height=9
ProcessBlock: ACCEPTED
Running BitcoinMiner with 1 transactions in block
BitcoinMiner:
proof-of-work found
hash: 00000040dc940b90423981994194bf3ae4ce58e665544c81f3aa7798785f24b7
target: 000000ffff000000000000000000000000000000000000000000000000000000
CBlock(hash=00000040dc940b, ver=0, hashPrevBlock=0000001aadb3ce, hashMerkleRoot=0e3474, nTime=1794807167, nBits=1e00ffff, nNonce=6066310, vtx=1)
CTransaction(hash=0e3474, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(000000, -1), coinbase 04ffff001e0102)
CTxOut(nValue=50.00000000, scriptPubKey=0x2FE48DB5E385E3D7F3AD2D)
vMerkleTree: 0e3474
AddToWallet 0e3474 new
AddToBlockIndex: new best=00000040dc940b height=10
ProcessBlock: ACCEPTED
sending: inv (37 bytes)
ProcessMessages(57 bytes)
received: getdata (37 bytes) 01 02 00 00 00 b7 24 5f 78 98 77 aa f3 81 4c 54 65 e6 58 ce e4 3a bf 94 41
received getdata for: block 00000040dc940b
sending: block (215 bytes)
这里又产生了两个区块,依旧不是分叉,是BitcoinMiner的机制,待会再说,测试是没问题的。
当我们同时按下回车后,双方都输出这个:
cpp
Running BitcoinMiner with 2 transactions in block
有2条交易,说明双方都在挖我们的这笔交易,按照我们的设定来的。
然后a节点先挖出来,广播给b节点后,b节点更新数据,更新了最优链。
然后BitcoinMiner会有这个判断:当最优链变化时。
cpp
if (pindexPrev != pindexBest)
break;
它就会停止这个区块的挖取,然后重新组装一个区块进行挖矿。
所以他产生了高度为10,第11个区块,然后再广播同步,可以看到b节点后一个挖矿有这个输出:
cpp
Running BitcoinMiner with 1 transactions in block
这并没有什么问题,其实这才是正常的逻辑,只是我们为了测试。
正常工作时,都是不停挖矿,不是别人挖到了,我就不挖了,我还要挖别的块。10分钟产生一个区块,只是我们难度很低,导致大量产生区块,好像不正常一样。
好,广播tx,多节点竟争挖矿,产生区块再广播区块多节点同步的功能已经没问题。
11.GetNextWorkRequired遗留问题
cpp
unsigned int GetNextWorkRequired(const CBlockIndex* pindexLast)
{
const unsigned int nTargetTimespan = 14 * 24 * 60 * 60; // two weeks
const unsigned int nTargetSpacing = 10 * 60;
const unsigned int nInterval = nTargetTimespan / nTargetSpacing;
//临时指定 手动调整难度
if ((pindexLast->nHeight + 1) == 7)
return 0x1e00ffff;
// Genesis block
if (pindexLast == NULL)
return bnProofOfWorkLimit.GetCompact();
然后是那个手动指定难度的问题,我是继续保留还是删除,如果要留着这条链,并且以后引入第三个节点,就不能删除那句指定代码,因为节点同步时,会重现难度获取。当计算的数字不对时无法通过。因为我已经删除返回0x1e00ffff代码,重新计算时是另一个值。对不上记录在链上的区块难度。
如果以后只是a,b节点的话,我查看了加载区块的代码,以及大概找了下其它的调用,比如引用的时候。没看到有动态计算验证。因为已经写好了。就像你引用你数据库的一笔tx,你不会检测这笔tx,本身是否合法。因为已经经过了检测才写入。只要在数据库里有,就代表了合法。他们的验证也是这样。但是如果在别人同步时,因为要写入数据库,所以还是会检查。会查所有的源头。
好,大概是这样回事,不必过多关注了,我们用来测试就行。实在不想去研究,就保留这句代码,为了不多事,我们保留。或者重新创一个链,从创世块开始。
好,我们接下来就可以解决孤块和链重组的问题。把这两个解决,核心功能就完成了。已经可以多节点转账了,不会说在特定的情况下才正常。