"vout": [
{
"value": [b]0.00020000,[/b]
I used the latest QT Litecoin Core version v0.10.2.2 (64-bit) I guess my question is how did this tx get accepted locally (and in other nodes) if it has insufficient fees to be confirmed? And why isnt 0.001 enough of a fee? Are you saying that if the output was bigger, the fee would have been enough? James Litecoin's stock policy has had this fee penalty for each too small output since 2011. Your code must calculate fees in the same manner or it will fail to relay or be mined by nodes operating under the stock policy. Nothing stops submitting a raw transaction to your own node, and some explorers accept non-standard transactions such as this, but the vast majority of the network will not accept it. You can test this by watching debug.log of any standard node. |
|
|
|
2015-09-07 16:23:58 ERROR: AcceptToMemoryPool : not enough fees 3b90916d8442342813c4b6415f699cdd2846f668881c7ce8f5966a16a3bf47f3, 100000 < 200000 It is not propagating because it has insufficient fees. There is no bug here. Can you dumprawtransaction and paste the output here? If you do I can explain why the fees are insufficient. I'm guessing it has an output that is too small and thus triggering the fee penalty? BTW, what client created this transaction? |
|
|
|
The whole appeal to authority hugely undermines the principles of the system. If you want something that lives and dies on the whim of some authority: centeralized systems can have much better performance and security properties.
This is a critically important point. |
|
|
|
theymos forgot to mention that most of the cost of the wiki (aside from the hosting and DDoS protection) is the upstream mediawiki developer we hired to make it suck a lot less. He has a lot of work ahead of him including ... - Keep the wiki updated, secure and with the latest features.
- Rewrite the cryptopayment plugin so it is suitable for open source, allowing anyone else to deploy it.
- Currently the non-English wikis are almost dead partly because of the terrible centralauth system, and the fact that each language is effectively another wiki, making it impossible to keep translations in line. He will deploy the mediawiki Translate plugin, then convert all of the non-English wikis to use the same login system.
- Time consuming task of reaching out to the many non-English communities and teaching them how the wiki no longer sucks with the translate plugin. They need to work on translating each page, one paragraph at a time.
|
|
|
|
|
The forum was under a big DDoS attack. theymos has long resisted the idea of protecting the forum with the most cost effective DDoS protection providers like Cloudflare because doing so hands the SSL private keys to a 3rd party company and increases the privacy risk of the users. Instead he decided to try hosting at another provider with automatic DDoS mitigation where theymos continues to directly control the SSL certificate. This provider is considerably more expensive than Cloudflare, which he considers necessary to protect the users. It remains to be seen if their service is reliable and worth the cost.
|
|
|
|
|
The forum was under a big DDoS attack. theymos has long resisted the idea of protecting the forum with the most cost effective DDoS protection providers like Cloudflare because doing so hands the SSL private keys to a 3rd party company and increases the privacy risk of the users. Instead he decided to try hosting at another provider with automatic DDoS mitigation where theymos continues to directly control the SSL certificate. He will see how things go with this new host provider.
|
|
|
|
|
The forum was under a big DDoS attack. theymos has long resisted the idea of protecting the forum with the most cost effective DDoS protection providers like Cloudflare because doing so hands the SSL private keys to a 3rd party company and increases the privacy risk of the users. Instead he decided to try hosting at another provider with automatic DDoS mitigation where theymos continues to directly control the SSL certificate. He will see how things go with this new host provider.
|
|
|
|
|
How is it bad? The fee is roughly 1 cent for most transactions now.
|
|
|
|
|
They plan on allowing you to trim down the previous quote to whatever lines you want. Since previous quotes are by reference I assume clicking through to the post or expanding it will also be possible. It's in the design phase now.
|
|
|
|
|
The new forum software is already planning to do quote replies by reference (post, version and line number) instead of by pasting duplicate blobs of text, so notifications upon replies is very much possible.
|
|
|
|
Status UpdateThanks to Cory Fields gitian deterministic builds for MacOS X are now an official part of the Bitcoin Core release process. These nightly builds now provide deterministic builds for Linux, Windows and MacOS X. Great work Cory Fields!
|
|
|
|
Status Updatehttp://nightly.bitcoin.it now has separate builds for the master and 0.9.2 branch. 0.9.2 is what will soon become the release while master is accepting changes that may not be safe for a near-term release. The release candidate for 0.9.2 was previously scheduled for May 13th. Yesterday it was decided to postpone this for 7 days due to the Bitcoin 2014 Amsterdam conference. The string freeze is now in effect and it is a very good time to contribute translations during these next 7 days.
|
|
|
|
|
Please request the feature in the new forum software section.
|
|
|
|
We are only two days away from the scheduled 0.9.2 release candidate. Now is a very good time to fix the translations. |
|
|
|
https://www.transifex.com/projects/p/bitcoin/We are approaching the deadline for Bitcoin Core 0.9.2. Many languages require translations. You can help even if you do not speak those languages by bringing attention to this thread of the native language communities. Can you help?
|
|
|
|
|
Show Posts
