Don't trust the priority thing that blockchain gives, a lot of time it is inaccurate.

Your problem is the low fee. At this time, your fee is not enough for the transaction which is 796 bytes. You will just need to wait a while for it to confirm.

As I said in my pm, you need to do a post request, which browsers do not do through the URL bar. You will need to put the URL in an HTML form that does post if it is on a webpage. Otherwise, it probably won't work.

Can you post the raw hex of a transaction you are trying to send? I will try to broadcast it from my node. If that works, then there must be something wrong with your bitcoin core installation.

To get the hex, send the transaction normally then right click it in the transaction list and click view details. Then click copy hex and then paste that to a post.

It was 0.00001

The dust threshold is not hard coded. It is determined by the minrelaytxfee. The dust threshold changes with what is set as the minrelaytxfee, so you can set the minrelaytxfee in your own node to the original default of 0.00001 instead of the new default of 0.00005. That will change your dust threshold.

There is something wrong with your bitcoin core installation which is making it reject the transactions. Do you have any special configuration for it that your are using?

I think I can do this. I will send you a PM. Will you escrow the funds?

Wangxinxi, you should update the OP so that the number of open slots are accurate.

blocktrail has a payments forwarding api: https://www.blocktrail.com/api/docs#payments_overview and so does blockcypher: http://dev.blockcypher.com/#payment-forwarding

That is an amazing list of stuff!

OP, you should also use some of the references in the bitcoin whitepaper

Yes. It's under expert mode.

There are tools to crack wallets but they only work if you have some idea of what the password is.

How about doing split key generation? If someone is generating a vanity address for someone, they should use split key so that the generator cannot steal bitcoin from that address.

You could flash your own firmware as people have done for hacking via USB.

I have developer account as well. It is not ready for publishing yet, it will be once I iron out all of the bugs and add the remaining features.

If you can make the ui look better, please do. Submit a pull request to the Github and I will take a look.

If you can do it, go ahead. Submit a PR and I will have a look.

The next version of the app, v0.6, has been finished

Notable changes:

• Posts can be quoted
• Your own posts can be edited and deleted by yourself
• New PMs can be sent
• PMs can be quoted and replied to
• Basic Notifications about new posts and messages added
• Notifications can be configured in settings

The release can be viewed on Github: https://github.com/achow101/BitcointalkForum/releases/tag/v0.66

Can you please clarify what "passphrase authentication for dev" is?

And what do you mean by "This data store in the blockchain?"?

As for storing data in the blockchain, this is not recommended since you will be bloating the blockchain. That is quite selfish. If you really want to though, there are a variety of methods. You can use OP_RETURN to store 40 bytes, or you can do other stuff with addresses and scripts to store your data.

yes you can. right now, since the blockchain has not forked, they both use the same blockchain. However, to run both programs simultaneously, you need to run them on different ports and each will need its own data directory.

I concur. My site measures post quality through an admittedly poor algorithm. The only true way to determine post quality is to read the post in context and that takes a very very complex algorithm or a person.