 | | Bitcoin Extra Wallet is an Android app built upon Andreas Schildbach's popular wallet, with additional features. You can use it to exchange and pay to altcoins using ShapeShift integration and you can export your transactions for accounting purposes. I have already developed the Peercoin Android wallet and NuDroid (for NuBits) which also have these additional features. The app is open-source under GPLv3.
ShapeShift Functionality
ShapeShift integration allows you to pay to alternative coins such as Peercoin or Litecoin with your Bitcoin. Simply scan a QR code, follow a payment link, or enter an address for a coin of choice. You can specify a Bitcoin amount or an amount in the other currency. When you send Bitcoin your funds will automatically be exchanged and sent. It couldn't be any simpler!
The supported coins are: BitCrystals, Blackcoin, Clams, Counterparty, Dash, Digibyte, Dogecoin, Emercoin, Litecoin, MaidSafeCoin, Mastercoin, Mintcoin, Monacoin, Namecoin, Novacoin, NuBits, Peercoin, Reddcoin, Shadowcash, Startcoin, Storjcoin X, Vericoin, and Vertcoin.
Ethereum is not currently supported, however may be added in an update. ShapeShift is not used for Bitcoin only transfers.
ShapeShift is a third party service: http://shapeshift.io
Other Features
- In the menu you can export your transactions to a csv file.
- No registration, web service or cloud needed! This wallet is de-centralized and peer to peer.
- Display of Bitcoin amount in BTC, mBTC and µBTC.
- Conversion to and from national currencies.
- Sending and receiving of Bitcoin via NFC, QR codes or Bitcoin URLs.
- Address book for regularly used Bitcoin addresses.
- When you're offline, you can still pay via Bluetooth.
- System notification for received coins.
- Sweeping of paper wallets (e.g. those used for cold storage).
- App widget for Bitcoin balance.
| |
|
|
|
|
|
If you have highly limited mobile data usage, I recommend using WiFi for the initial download if possible. The initial download uses block headers only, but you can still be looking at about ~50mb of data to download.
|
|
|
|
|
75% is way too low. There needs to be a strong consensus. 25% of miners disagreeing is a lot.
|
|
|
|
Hi Andrew, I have worked on full validation on cbitcoin, though I decided to scrap it in favour of more primitive bitcoin functions only, because of the time and work involved in getting it fully functional and tested. cbitcoin however would give a set of tools to help with creating a fully validating node, and the CBNetworkCommunicator code goes some way to implementing a node (handshakes, pings, peer discovery etc.). For blockchain validation you could look at the old CBValidator code, though I removed it. The library still has things such as address encoding, BIP0032 HD Wallets, message structures inc. serialisation, basic validation functions (merkle tree functions, proof of work stuff etc.), script creation/execution, and transaction creation/signing. However to create an alt-coin from it would be an unnecessary difficulty in my opinion, though it could make an interesting project for sure, and cbitcoin may be useful in projects, though I can't guarantee that it's 100% correct and bug free. I am personally using the HD wallet code in another project with some modifications. I also use the example programs quite a lot: https://github.com/MatthewLM/cbitcoin/tree/master/examplesRegards, Matthew |
|
|
|
Can we push it into student's syllabus learning C ? If yes, how ? Any idea ?
There was one university project using cbitcoin. I'm not sure how much they would be happy for me to disclose about that though. I changed cbitcoin significantly in a new commit. I removed a lot of incomplete code so that what is left is done to a higher degree of completeness. It has code for HD wallets, transaction construction, script execution/construction, network messages, bitcoin addresses, WIF addresses, general base58 encoding/decoding, basic network communication, proof of work validation and more. |
|
|
|
I'm sorry but this coin is dead. I tried to contact the coin's management with no luck many times. I closed hashaxe in the end. There's no point. I did consider reviving the coin under new management but I can't do it myself, I'd need volunteers to help.
Moments ago the EMC2 board adopted the measure to move forward with plans to be involved with the Ebola project. The extent of our involvement is contingent on our own community's commitment to the endeavor as well as the various levels of commitment other communities are expected to pledge. Our board has approved leadership resources, social networking resources, and 1 Million EMC2 coins for the effort; these are all minimums; its important to note that since the endeavor is far larger than all of our previous endeavors we are seeking community ratification. The project requires strategic partners, not just for currency but for leadership and volunteers as well. An exploratory committee made up of representatives of each of the involved cause coin will determine if they move forward to take on the project and if so the scope of the project, what the respective communities could be expected to responsibly pledge, and the best way to address the goals of the project. Currently two coins are committed to the effort: EMC2 and WorldAidCoin. Mathew please consider joining forces for this effort and perhaps other projects, I know you said the coin is dead but let's talk about a merge of sorts -- let's talk. Hi, I'm not able to take a detailed look into this now, but please do leave me an email or private message about any proposal and I'll take a look when I next can. Regards, Matthew |
|
|
|
|
I'm sorry but this coin is dead. I tried to contact the coin's management with no luck many times. I closed hashaxe in the end. There's no point. I did consider reviving the coin under new management but I can't do it myself, I'd need volunteers to help.
|
|
|
|
|
That's the problem. There was a problem where a double spend would remain in the wallet and the wallet would try to spend from unconfirmed double spends, so you would try to make transactions but they would end up unconfirmed.
Using -salvagewallet is one way to fix this, but it shouldn't be a problem in the first place. I'm wondering if it is fixed?
Also the software should not spend unconfirmed outputs, that's a bad idea.
|
|
|
|
I know that in at least earlier versions of bitcoins there was a significant problem with transactions that would never confirm due to double spend: https://bitcointalk.org/index.php?topic=85689.0Has this problem been resolved? If so, which version? And if anyone could point to the particular code/commit that fixes it, I would be most grateful. Thanks, Matthew |
|
|
|
|
If anyone was struggling to connect to hashaxe's stratum, it is now working OK.
|
|
|
|
|
Here's a tutorial for the zk-SNARKs:https://github.com/scipr-lab/libsnark/blob/master/src/gadgetlib2/examples/tutorial.cpp
Very low level, and it doesn't demonstrate circuit loops, but interesting nonetheless. Looking forward mostly for the TinyRAM circuit generator.
|
|
|
|
|
Well hopefully there is a way to generate the parameters in a trust-less way, they just don't know how yet.
|
|
|
|
|
"We're building a system that will not have a back door"... Well there's no way of knowing that the security parameters do not contain a back door, so we have to trust the people who generate them. Hopefully someone will figure out a way to generate them in a provably trustworthy fashion. I don't know if that's possible.
|
|
|
|
|
Blocks are now coming through!
The reason the block took so long is because the time warping caused the difficulty to go very high. It demonstrates the KGW is flawed in more ways than previously expected. I would personally recommend using a SMA for difficulty adjustments in any coin. The reason I used KGW, is because it was popular, and despite it's convolutedness, I expected it to be well tested and safe. But that was not the case. I can only learn to always check the code myself!
I still see no evidence of a fork. The only thing that seems to have happened is someone was using Charitycoin as a test-bed for time warping. How very nice of them (sarcasm).
If the network hashrate remains high, it makes it difficult for anyone to cause significant time warping. Until a time comes when the algorithm is changed, this is the best defence. So keep mining!
Regards,
Matthew.
|
|
|
|
|
For some reason the MPOS software on my pool got confused. Someone has tried to do time-warping with the network which is probably the reason. Now no blocks seem to be going through. I've restarted the server, so maybe things will work now, but there are no miners on the pool to test it yet.
I can't see any obvious evidence of a blockchain fork, because I see no "orphan" (which should be called "side-chain blocks") blocks reported by MPOS, but I'm not sure how much I can trust the information provided by MPOS.
I can't see any obvious information in any logs that can help.
If anyone else has any details please get in touch.
Matthew.
Edit: If anyone can or can't solo mine, please let me know.
Edit 2: No blocks are coming through. When I get chance I'll be able to take a closer look.
|
|
|
|
|
cbitcoin is now using the MIT license.
|
|
|
|
|
Show Posts
