回复：版本 0.3.13，请升级
原始发布页
打开来源页面查看 1 个交叉存档
引用 theymos 于 2010 年 10 月 03 日 08:09:51 PM 的发言
ArtForz 已经在免交易费运行，而且他拥有全网 20-30% 的 CPU 算力。不过，最初发送那些有问题交易的人删除了自己的钱包，而网络已经忘记了这些历史交易，所以任何以此为基础的交易都不会得到确认。
在你的节点拥有一条能够回溯到区块链的交易路径之前，交易不会被接受，也不会显示为 0/未确认。
你钱包中的任何交易也都捆绑了为抵达区块链所需的全部未记录交易。如果你有一笔显示为 0/未确认的交易，那么你也拥有它所依赖的全部先前未记录交易；当你重新广播自己的交易时，也会重新广播那些交易。
如果已经生成了一个免交易费区块，却没有起到作用，那我就需要看看问题出在哪里。这部分代码不太常用。每个拥有依赖于这些交易之交易的人，其钱包中都应该记录着它们。
引用 theymos 于 2010 年 10 月 03 日 08:09:51 PM 的发言
最初发送那些有问题交易的人删除了自己的钱包
唉……为什么要删除钱包，而不是把它移到一旁并保留旧副本以防万一？你永远都不该删除钱包。
引用 tcatm 于 2010 年 10 月 03 日 08:10:47 PM 的发言
它正在运行。应该能在 3 小时内找到一个区块。
收集重新广播的交易可能需要一段时间。如果你能接受入站连接，就会监听更多节点，这会有帮助。即使你在 3 小时内找到了一个区块，也请让它持续运行至少几天。
英文原文
展开英文原文
Quote from: theymos on October 03, 2010, 08:09:51 PM
ArtForz is already running with no fees, and he has 20-30% of the network's CPU power. The person who originally sent the broken transactions deleted his wallet, though, and the network has forgotten these historical transactions, so any transactions based on this won't confirm.
Transactions aren't accepted or displayed as 0/unconfirmed until your node has a path of transactions back to the block chain.
Any transactions in your wallet also have bundled with them all unrecorded transactions required to reach the block chain. If you have a transaction that is displayed as 0/unconfirmed, then you have all the previous unrecorded transactions it depends on and you will also rebroadcast those transactions when you rebroadcast yours.
If a no-fee block has already been generated and hasn't helped, then I need to look at what's wrong. It's a part of code that doesn't get much use. They should be recorded in the wallets of everyone who has a transaction depending on them.
Quote from: theymos on October 03, 2010, 08:09:51 PM
The person who originally sent the broken transactions deleted his wallet
Sigh... why delete a wallet instead of moving it aside and keeping the old copy just in case? You should never delete a wallet.
Quote from: tcatm on October 03, 2010, 08:10:47 PM
It's running. Should find a block within 3 hours.
It may take a while to collect re-broadcast transactions. It'll help if you can accept inbound connections so you'll be listening to more nodes. Even if you find a block in 3 hours, keep it running continuously for a few days at least.