BitShares Forum
Main => General Discussion => Topic started by: ElMato on December 01, 2014, 08:57:20 am
-
-------------------
ALPHA2 UPDATE
-------------------
--------------
IMPORTANT
--------------
* Follow the "How to upgrade" instructions if you have alpha-1 installed.
* If you plan to transfer funds from desktop wallet to mobile, don't use the GUI because it will generate a titan transaction that the mobile wallet wont see. (If it happens by mistake PM me and i will help you recovering those funds)
use wallet_transfer_to_address 5 USD your_account your_address_in_mobile from console.
---------------------
HOW TO UPGRADE
---------------------
1) Export your wallet
2) Install alpha2
3) Restore wallet
-----------------------
SCREENSHOTS & APK
-----------------------
https://www.dropbox.com/sh/0xfnkep3u1dvjmt/AABVmvgXx3tb2mf3QqAj8yBKa?dl=0
Bitwallet-debug.apk shasum f71c67062343232b3ddf4e6bdf6d08c64801b836
-------------
CHANGELOG
-------------
* i18N ready.
- english
- spanish
- russian [thanks testz]
- korean [thanks clayop]
- chinese [thanks btswildpig]
- italian [thanks spartako]
* Send to registered name (non-TITAN)
* Scan publickey
* Scan paper wallet
* Multicurrency CNY/USD/BTC/Gold
* Local address book
----------------------------------------------------------------------
Dear community,
My name is Matias Romeo and together with Pablo Tutino we are both cofounders of Latincoin.com.
We are based in Buenos Aires (Argentina) working from the "Bitcoin Center Buenos Aires" (aka: Bitcoin Embassy)
As many of you know the current situation in our country is one of a big opportunity for bitUSD, and seeing that the mobile wallet for bitshares is lagging behind we decided to do our contribution and started the development of a mobile bitasset wallet.
We think that Argentina has a lot of potential for the daily use of bitUSD and we have a lot of efforts going on in that sense that hope to release soon.
----------------------------------------------------------------------------------------------
This is highly alpha software so if you plan to use it do not put large sums of money.
----------------------------------------------------------------------------------------------
Source code here
https://github.com/latincoin-com/bitwallet
Screenshots and apk
https://www.dropbox.com/sh/0xfnkep3u1dvjmt/AABVmvgXx3tb2mf3QqAj8yBKa?dl=0
All the keys can be recovered from the master key, so it is recommended that you backup your wallet after installing the app.
------------------------------------------------
It will only work on Android 4.0+ (for now)
------------------------------------------------
In fact it runs on iOS, but the performance is too bad because of the JS engine.
We are working on a native iOS/Android plugin for the crypto part.
How does it work?
The client is in control of the private keys.
It uses a public API to create an unsigned transaction, then it signs it on client side, and push it to the network.
(See API below)
How do i send money to the wallet?
Select and address from the "My Addresses" list and use the wallet_transfer_asset_to_address command from the console (in the desktop wallet).
e.g.: wallet_transfer_asset_to_address 5 USD my_account BTSX9pTBfYkFwmUm46XTaeTLukGDrupobHwzc
Why i can't send to an account name?
It is planned for the next release.
Why i can't register my "account"?
It is planned for the next release.
What crypto library are you using?
We use bitcoinjs-lib 1.2.0 (with our bts.js to encode in BTS way) for the Hierarchical keys + Signing and CryptoJS for the AES encryption/decryption of the wallet.
Why USD only?
It is trivial to support other bitAssets, but we want to focus on bitUSD first.
In the following releases you will be able to switch from one bitAsset to another.
Why the apk is so big?
Chrome runtime is bundled within the ape (two architectures x86+arm )
We are using cross-walk library in order to use the latest Chrome runtime for android and to support
Why it looks so bad in my XXXXX device?
We are in alpha, give us some time to fix the design.
Other bugs and limitations:
- Client does not validate the transaction generated on the server. (Is the transaction doing what i asked for?)
- Only for newly created keys (from block 900000+)
- SSL Certificate error alert: xwalk lib is built with --check-web-security and we are using a self signed certificate in our WebSocket server (bswws.latincoin.com)
- Balance/Transaction history not refreshed after wallet restore. (Need to quit and run again)
- Export does not include address book.
- Unable to select an address from the address book when sending.
- Unusable on iOS
- Transaction details duplicates withdraws and deposits records.
- Rounding errors in balance.
## API
(doc coming soon)
This api lets you create an unsigned transaction using funds from many addresses and sending to many addresses.
POST https://bsw.latincoin.com/api/v1/txs/new
{
"asset" : 22,
"fee" : 250,
"from" : [{"address":"BTSX9pTBfYkFwmUm46XTaeTLukGDrupobHwzc"}],
"to" : [{
"address" : "BTSXF9WuaEqYn5sZJQGK6qzR8S9jRehUgQXzZ",
"amount" : 50000
}]
}
After that you have to sign the transaction digest (to_sign parameter in response json) with the corresponding private keys asked by required_signatures.
Add those signatures to a "signatures" parameter in "tx" json object and push it back to
https://bsw.latincoin.com/api/v1/txs/send
This api lets you know the balance and transaction history of an address.
GET https://bsw.latincoin.com/api/v1/addrs/BTSX9pTBfYkFwmUm46XTaeTLukGDrupobHwzc/balance
GET https://bsw.latincoin.com/api/v1/addrs/BTSX9pTBfYkFwmUm46XTaeTLukGDrupobHwzc,BTSXF9WuaEqYn5sZJQGK6qzR8S9jRehUgQXzZ/balance
GET https://bsw.latincoin.com/api/v1/addrs/xpub661MyMwAqRbcEYS8w7XLSVeEsBXy79zSzH1J8vCdxAZningWLdN3zgtU6T6MHAZTgj9H6QNfLWByR1Dj4exUQ8FqYv9s7KecprYm7unUkX1:5/balance
It also support BIP32 Extended pub key format. (5 is the number of derivations)
There is also a websocket subscription mechanism to notify you when funds have been received or sent from a group of addresses.
wss://bswws.latincoin.com
sub BTSX9pTBfYkFwmUm46XTaeTLukGDrupobHwzc
sub xpub661MyMwAqRbcEYS8w7XLSVeEsBXy79zSzH1J8vCdxAZningWLdN3zgtU6T6MHAZTgj9H6QNfLWByR1Dj4exUQ8FqYv9s7KecprYm7unUkX1:5
-
BAM!!!!
Awesome .. +5%
BTW, "BTSX" should be "BTS" .. also in the addresses and pubkeys
Questions:
- Privkeys are on the device only?
- can you offer a precompile APK?
- screenshots?
-
BAM!!!!
Awesome .. +5%
Thanks!!!
BTW, "BTSX" should be "BTS" .. also in the addresses and pubkeys
Is version 0.4.24 already working with the BTS prefix?
Questions:
- Privkeys are on the device only?
Yes, private keys are on the device only.
- can you offer a precompile APK?
- screenshots?
I will update the post ...
Updated
-
Indeed great news! Screenshots etc. much appreciated…
-
i'll provide a logo etc. later this day
and it would be also a great pleasure to assist you on coloring etc...
if you want me to help…just said
and i want to point to also to another post here... this could be interesting for both parties :)
matt608 delegate proposal
https://bitsharestalk.org/index.php?topic=11847.0
-
here are some screenshots, i extracted it from dropbox and uploaded to imgur
http://imgur.com/a/HTkmb
(http://i.imgur.com/nVBkTSY.png)
(http://i.imgur.com/9uuK681.png)
(http://i.imgur.com/1HPQ4ml.png)
-
nice!
I think we need hire some people to check the source code develop by the third party, any idea?
-
This is awesome! So since this is simply a wrapper for a JS library and an angular wallet, this could easily be used to make an online web wallet too no?
And I suppose it only works for non-TITAN addresses?
-
i'll provide a logo etc. later this day
and it would be also a great pleasure to assist you on coloring etc...
if you want me to help…just said
and i want to point to also to another post here... this could be interesting for both parties :)
matt608 delegate proposal
https://bitsharestalk.org/index.php?topic=11847.0
@cass it will be great if you can help us on every aspect of the design! not just coloring but UX/UI.
Will pm you when i wake up today (6:50 am here!)
We will definitely contact matt608 and matador123, i can also meet him in person this week if he is in BA!
-
i'll provide a logo etc. later this day
and it would be also a great pleasure to assist you on coloring etc...
if you want me to help…just said
and i want to point to also to another post here... this could be interesting for both parties :)
matt608 delegate proposal
https://bitsharestalk.org/index.php?topic=11847.0
@cass it will be great if you can help us on every aspect of the design! not just coloring but UX/UI.
Will pm you when i wake up today (6:50 am here!)
We will definitely contact matt608 and matador123, i can also meet him in person this week if he is in BA!
contact me via skype, PMed!
-
nice!
I think we need hire some people to check the source code develop by the third party, any idea?
It would be great to have other "eyes" check our work.
We will talk with Sergio (Lerner) to see if he can do a security audit on the wallet.
-
And I suppose it only works for non-TITAN addresses?
Yep ..
Report:
I just installed the wallet .. send 5bitUSD to my ADDRESS and received it almost instantly ..
Picked one of my addresses from "wallet_account_list_public_keys" and sent back 1bitUSD .. has not arrived :(
Is the wallet sending via TITAN?
awesome job still
-
This is awesome! So since this is simply a wrapper for a JS library and an angular wallet, this could easily be used to make an online web wallet too no?
And I suppose it only works for non-TITAN addresses?
@svk, yes you are right it can be used to make an online wallet.
What we have done has two parts:
1) A basic blockchain web infrastructure for bitAssets. ( "like" blockcypher.com )
- Get address balance
- Get address transaction history
- Create unsigned transaction
- Broadcast signed transaction
- WebSocket callback when address balance has changed. (we need http webhooks)
2) A client application that.
- Has the private keys.
- Sign transactions.
TITAN is not used in the wallet.
We give the user the ability to create as many address as he wants.
And soon he will have some control over which "source addresses" (coin control) he wants to use in the transaction achieving a high level of privacy.
-
And I suppose it only works for non-TITAN addresses?
Yep ..
Report:
I just installed the wallet .. send 5bitUSD to my ADDRESS and received it almost instantly ..
Picked one of my addresses from "wallet_account_list_public_keys" and sent back 1bitUSD .. has not arrived :(
Is the wallet sending via TITAN?
awesome job still
Strange ... i have done the same and it worked fine.
Maybe the transaction didn't get through.
Did your balance lower by 1 usd?
(Transactions are created with 30s deadline, so if more than 30s passed and you didn't received the amount, you can safely send it again because the blockchain will reject the previous transaction)
-
I can see that the transaction 27f58bf2eed0681c4630d9ef4267b6a7002360c0 IS depositing to the right address ... so maybe it's my wallet that didn't see it yet ..
-
Maybe a wallet_rescan_blockchain from one block before the transaction's block?
-
Maybe a wallet_rescan_blockchain from one block before the transaction's block?
yhea .. tried that already .. not showing up .. gonna rescan the whole thing ..
don't take to much effort in this as it CLEARLY is an issue of my wallet not seeing that the tx is for me .. the blockchain sees the tx .. so your mobile wallet is doing fine ..
-
I can see that the transaction 27f58bf2eed0681c4630d9ef4267b6a7002360c0 IS depositing to the right address ... so maybe it's my wallet that didn't see it yet ..
I'm gonna have to add some features for non-TITAN addresses I think so we can track transfers like this.
-
Maybe you can bring a online wallet example online!?
This would be really nice°
-
@OP: if you allowed to scan for Public keys .. you can derive the address for the public key in the mobile wallet ..
it's much easier currently to figure out a public key than it is to find addresses
you could also take registered names then .. get the pubkey registered with it and convert to an address
-
good news
-
And pls keep in mind :) , chinese Community members are directly offering help on chinese translation!
But not enough, me & xeroc will also help translating into german. Also i can provide netherland translations …
@testz: could you ask for russian translations!?
Languages
- Chinese
- Germany / xeroc (https://bitsharestalk.org/index.php?action=profile;u=120)
- Netherlands cass (https://bitsharestalk.org/index.php?action=profile;u=224)
- Russian (testz?) testz (https://bitsharestalk.org/index.php?action=profile;u=183)
And somebody should check git/code if malicious content is included etc.! Maybe Sergrio!?
@ElMato: no offense, you know…this should get done on all 3rd developers apps etc.. and on 3i apps also
-
great work and good news,if you can contact cn-members for some translate,more chinese can read this.
-
great work and good news,if you can contact cn-members for some translate,more chinese can read this.
translation into chinese is in progress
-
And pls keep in mind :) , chinese Community members are directly offering help on chinese translation!
But not enough, me & xeroc will also help translating into german. Also i can provide netherland translations …
@testz: could you ask for russian translations!?
Languages
- Chinese
- Germany
- Netherlands
- Russian (testz?)
And somebody should check git/code if malicious content is included etc.! Maybe Sergrio!?
@ElMato: no offense, you know…this should get done on all 3rd developers apps etc.. and on 3i apps also
Exactly. We can dochinese translation.
Also, I installed it on my android phone and found that its balance only shows USD. I wonder whether this could be changable? Cuz people in china for example would difinitely want to use CNY by default.
Thanks again for your effort.
-
french translation @svk ?
Update:
- I successfully sent 1bitUSD back to my on-mobile account .. that worked
- I added an address to my addressbook (from a receiving tx) .. but cannot access the address book anywhere :(
- a second outgoing tx to my full-node client did also not go through .. tested a different address from "list_public_keys" :( .. odd .. loss so far just 1.10$
-
This is the kind of 100% delegate I would vote for .
+5% +5% +5%
-
This is a really great development. +5%
Once I am elected as marketing delegate there will be a campaign directing targeted traffic to a bitUSD portal (in development) customised for the Argentine and Spanish speaking market. The users will then be directed to exchanges where they can buy bitUSD. This is great news as latincoin.com can be one of them!
PMd
-
french translation @svk ?
Update:
- I successfully sent 1bitUSD back to my on-mobile account .. that worked
- I added an address to my addressbook (from a receiving tx) .. but cannot access the address book anywhere :(
- a second outgoing tx to my full-node client did also not go through .. tested a different address from "list_public_keys" :( .. odd .. loss so far just 1.10$
Can do French for sure but seems like there's no localization framework in place? Would be easier to provide translations if they added angular translate to handle localizations.
-
And pls keep in mind :) , chinese Community members are directly offering help on chinese translation!
But not enough, me & xeroc will also help translating into german. Also i can provide netherland translations …
@testz: could you ask for russian translations!?
Languages
- Chinese
- Germany
- Netherlands
- Russian (testz?)
And somebody should check git/code if malicious content is included etc.! Maybe Sergrio!?
@ElMato: no offense, you know…this should get done on all 3rd developers apps etc.. and on 3i apps also
Exactly. We can dochinese translation.
Also, I installed it on my android phone and found that its balance only shows USD. I wonder whether this could be changable? Cuz people in china for example would difinitely want to use CNY by default.
Thanks again for your effort.
+5%
-
french translation @svk ?
Update:
- I successfully sent 1bitUSD back to my on-mobile account .. that worked
- I added an address to my addressbook (from a receiving tx) .. but cannot access the address book anywhere :(
- a second outgoing tx to my full-node client did also not go through .. tested a different address from "list_public_keys" :( .. odd .. loss so far just 1.10$
Can do French for sure but seems like there's no localization framework in place? Would be easier to provide translations if they added angular translate to handle localizations.
agreed this would make sense…
-
+5%
Great!
-
Awesome .. +5%
let us vote you as 100% pay rate delegate
-
Great work! I'm testing right now...
This is the kind of 100% delegate I would vote for .
+5% +5% +5%
You should create a delegate for sure!
-
Dear community,
My name is Matias Romeo and together with Pablo Tutino we are both cofounders of Latincoin.com.
We are based in Buenos Aires (Argentina) working from the "Bitcoin Center Buenos Aires" (aka: Bitcoin Embassy)
As many of you know the current situation in our country is one of a big opportunity for bitUSD, and seeing that the mobile wallet for bitshares is lagging behind we decided to do our contribution and started the development of a mobile bitasset wallet.
We think that Argentina has a lot of potential for the daily use of bitUSD and we have a lot of efforts going on in that sense that hope to release soon.
----------------------------------------------------------------------------------------------
This is highly alpha software so if you plan to use it do not put large sums of money.
----------------------------------------------------------------------------------------------
Source code here
https://github.com/latincoin-com/bitwallet
Screenshots and apk
https://www.dropbox.com/sh/rq23wm41xqmha3s/AABkh-k8B7P_V6KJ5X5fS4S0a?dl=0
(https://dl-web.dropbox.com/get/bw_small.gif?_subject_uid=8785004&w=AAB7mPrg9Iy9az26LNwg08atgsM7mYnoM7crzmxjwdnAjg)
All the keys can be recovered from the master key, so it is recommended that you backup your wallet after installing the app.
------------------------------------------------
It will only work on Android 4.0+ (for now)
------------------------------------------------
In fact it runs on iOS, but the performance is too bad because of the JS engine.
We are working on a native iOS/Android plugin for the crypto part.
How does it work?
The client is in control of the private keys.
It uses a public API to create an unsigned transaction, then it signs it on client side, and push it to the network.
(See API below)
How do i send money to the wallet?
Select and address from the "My Addresses" list and use the wallet_transfer_asset_to_address command from the console (in the desktop wallet).
e.g.: wallet_transfer_asset_to_address USD 5 my_account BTSX9pTBfYkFwmUm46XTaeTLukGDrupobHwzc
Why i can't send to an account name?
It is planned for the next release.
Why i can't register my "account"?
It is planned for the next release.
What crypto library are you using?
We use bitcoinjs-lib 1.2.0 (with our bts.js to encode in BTS way) for the Hierarchical keys + Signing and CryptoJS for the AES encryption/decryption of the wallet.
Why USD only?
It is trivial to support other bitAssets, but we want to focus on bitUSD first.
In the following releases you will be able to switch from one bitAsset to another.
Why the apk is so big?
Chrome runtime is bundled within the ape (two architectures x86+arm )
We are using cross-walk library in order to use the latest Chrome runtime for android and to support
Why it looks so bad in my XXXXX device?
We are in alpha, give us some time to fix the design.
Other bugs and limitations:
- Client does not validate the transaction generated on the server. (Is the transaction doing what i asked for?)
- Only for newly created keys (from block 900000+)
- SSL Certificate error alert: xwalk lib is built with --check-web-security and we are using a self signed certificate in our WebSocket server (bswws.latincoin.com)
- Balance/Transaction history not refreshed after wallet restore. (Need to quit and run again)
- Export does not include address book.
- Unable to select an address from the address book when sending.
- Unusable on iOS
- Transaction details duplicates withdraws and deposits records.
- Rounding errors in balance.
## API
(doc coming soon)
This api lets you create an unsigned transaction using funds from many addresses and sending to many addresses.
POST https://bsw.latincoin.com/api/v1/txs/new
{
"asset" : 22,
"fee" : 250,
"from" : [{"address":"BTSX9pTBfYkFwmUm46XTaeTLukGDrupobHwzc"}],
"to" : [{
"address" : "BTSXF9WuaEqYn5sZJQGK6qzR8S9jRehUgQXzZ",
"amount" : 50000
}]
}
After that you have to sign the transaction digest (to_sign parameter in response json) with the corresponding private keys asked by required_signatures.
Add those signatures to a "signatures" parameter in "tx" json object and push it back to
https://bsw.latincoin.com/api/v1/txs/send
This api lets you know the balance and transaction history of an address.
GET https://bsw.latincoin.com/api/v1/addrs/BTSX9pTBfYkFwmUm46XTaeTLukGDrupobHwzc/balance
GET https://bsw.latincoin.com/api/v1/addrs/BTSX9pTBfYkFwmUm46XTaeTLukGDrupobHwzc,BTSXF9WuaEqYn5sZJQGK6qzR8S9jRehUgQXzZ/balance
GET https://bsw.latincoin.com/api/v1/addrs/xpub661MyMwAqRbcEYS8w7XLSVeEsBXy79zSzH1J8vCdxAZningWLdN3zgtU6T6MHAZTgj9H6QNfLWByR1Dj4exUQ8FqYv9s7KecprYm7unUkX1:5/balance
It also support BIP32 Extended pub key format. (5 is the number of derivations)
There is also a websocket subscription mechanism to notify you when funds have been received or sent from a group of addresses.
wss://bswws.latincoin.com
sub BTSX9pTBfYkFwmUm46XTaeTLukGDrupobHwzc
sub xpub661MyMwAqRbcEYS8w7XLSVeEsBXy79zSzH1J8vCdxAZningWLdN3zgtU6T6MHAZTgj9H6QNfLWByR1Dj4exUQ8FqYv9s7KecprYm7unUkX1:5
Well done. Hope more stalbe ,flexiable and easy for using bitwallet will come before this Christ. Ev.
-
Great work!!!
-
This is wonderful and unexpected news.
Please consider running a delegate and staying on in the future I know you will get some votes.
google nexus5
android 4.4.4 (dirty unicorns rom)
Just installed the wallet I get a ssl certifcate error but thats not a big deal just mentioning it.Installed and works fine so far
When I look for my address it shows me a bitcoin like address. Is their anyway we can change it to just names like in the client?
-
This is the kind of 100% delegate I would vote for .
+5% +5% +5%
+5%
-
We translated the thread into Chinese.
https://bitsharestalk.org/index.php?topic=11912.0
ElMato, Great work! +5%
-
Very good!
-
And pls keep in mind :) , chinese Community members are directly offering help on chinese translation!
But not enough, me & xeroc will also help translating into german. Also i can provide netherland translations …
@testz: could you ask for russian translations!?
Languages
- Chinese
- Germany / xeroc (https://bitsharestalk.org/index.php?action=profile;u=120)
- Netherlands cass (https://bitsharestalk.org/index.php?action=profile;u=224)
- Russian (testz?) testz (https://bitsharestalk.org/index.php?action=profile;u=183)
And somebody should check git/code if malicious content is included etc.! Maybe Sergrio!?
@ElMato: no offense, you know…this should get done on all 3rd developers apps etc.. and on 3i apps also
Sure we will do Russian translation :)
-
This is actually very impressive. Sounds like you could help with a thin client / web wallet, if you ask for a paid delegate position to do this you would get voted in in a heartbeat.
Watch out for API changes in the next version (for example "transfer_asset_to_address" might be renamed).
-
Great job. Ditto on you creating a 100% delegate.
I have a few questions:
- Does the Android client validate that the transaction to be signed returned by the server is one which sends X BitUSD to Y address where X and Y are the same as the one displayed in the confirmation to the user? This way if the receiving address was added to the local address book with a convenient label, the user could conveniently know that they are sending the right amount of money to the right place without having to trust that the server wasn't compromised to return a fake spending transaction (assuming the client executable wasn't compromised of course).
- Do you plan to allow the server to create and the client to sign (and ideally partially validate) an outgoing transaction to a TITAN address? In other words, a one-time private key is deterministically generated in the client, the client contacts the server with the one-time public key and the BTS account name of the receiver in order to create a new transaction that sends the BTS user some amount of BitUSD, the server returns the transaction the client needs to sign along with the receiving user's active public key (as claimed by the server), and the client checks the returned transaction to ensure the appropriate amount of BitUSD will be sent to the appropriate receive address that is derived from the one-time private key and the server-returned active public key. This way if the active public key of a BTS user was added to the local address book, the client could send money to a TITAN address without having to trust that the server returned a correct transaction. This only pertains to sending money to TITAN accounts and not receiving money to (and being able to spend that money from) a TITAN account, thus it would not require any of the mail server support for lightweight clients.
- Do you plan to support multisig addresses like 2-of-3 where one of the keys is held by the server and the server only signs the transaction after verifying the real user's intent with two-factor authentication? The API to create an outgoing transaction could be similar to the current one except the user would also need to type in a one-time password (either time-based from a separate hardware device or from an SMS message sent by the server) to spend funds and that one-time password would be included along with the necessary signatures in the POST to /api/v1/txs/send.
-
I got a error message "Ssl Certificate Error Alert" while launching the wallet. Any idea?
-
What about TITAN addresses, are they supported? Makes it much more user friendly.
Mike
-
And I suppose it only works for non-TITAN addresses?
Yep ..
Thats a shame. Thats some good stuff though. +5%
-
@abit: ssl warning is due to self-sign certificates on their backend
@mike623317: no TITAN .. possibly never .. due to the ECC tech and transaction scanning requirement
-
Dear community,
My name is Matias Romeo and together with Pablo Tutino we are both cofounders of Latincoin.com.
We are based in Buenos Aires (Argentina) working from the "Bitcoin Center Buenos Aires" (aka: Bitcoin Embassy)
As many of you know the current situation in our country is one of a big opportunity for bitUSD, and seeing that the mobile wallet for bitshares is lagging behind we decided to do our contribution and started the development of a mobile bitasset wallet.
We think that Argentina has a lot of potential for the daily use of bitUSD and we have a lot of efforts going on in that sense that hope to release soon.
+5% +5% Fantastic! And based in Argentina! Brilliant!!!
-
@mike623317: no TITAN .. possibly never .. due to the ECC tech and transaction scanning requirement
Certainly supporting TITAN should not be a priority for the mobile wallet, but I think "never" is too strong. TITAN should definitely be eventually made available on mobile clients since mobile users want privacy too.
I don't see how the ECC tech would make it limited to desktops/laptops but not suitable for mobile (assuming only relevant transactions are processed). The transaction scanning requirement is the only problem with mobile clients. The full blockchain should of course not be processed on a mobile device but that is the reason for the mail server: to notify the client about the subset of transactions in the blockchain meant for the user so that the client can selectively retrieve from the server and process the data for only those transactions.
I think better compatibility between TITAN and non-TITAN usage is really important. Full clients should easily be able to withdraw funds from their TITAN balances or non-TITAN addresses and send the funds privately to TITAN accounts and publicly to non-TITAN addresses (in both cases with an encrypted memo and private sender information included). Mobile clients should be able to publicly withdraw funds from their non-TITAN addresses and send them to TITAN accounts and non-TITAN addresses (again an encrypted memo could be included as well as the private sender information, but the sender information would in most cases would not really be private since the public will know the sender is associated with the public non-TITAN address the funds were withdrawn from). The only permutation left is mobile clients withdrawing funds from TITAN balances and sending them to TITAN accounts and non-TITAN addresses, which is not feasible without the mail server (that is the very low priority feature).
I would like to see the same UX on full clients and mobile clients in which a checkbox distinguishes whether the transfer was going to the user's public balance (the non-TITAN address corresponding to their active public key) or to their private balance (regular TITAN procedure). In either case, I think the to field should be the user's BTS account name (or a local alias) and not the ugly addresses. In the case of the mobile client, the client could retrieve the active public key of a BTS account name from the server and just trust the server is honest, or the user could pin the active public key along with the corresponding BTS account name to their address book after verifying out-of-band that it is correct (bonus points for a feature in the mobile client that allows trading this contact information between two smartphones automatically using NFC or Bluetooth).
-
Great job! We really need a mobile client for marketing to the masses. Are you running a delegate that I can vote for?
-
I tried transfer in and out and both succeeded.
steps:
1.run this command in the console of the pc wallet:
wallet_get_account my_account_name
2.copy the address after "account_address" to the mobile wallet
3.click the send button in mobile wallet
result:
1.balance in the pc wallet updated in seconds
2.mobile wallet keep showing the trx is pending for a long time, back to normal after a restart.
-
Fantastic work, this is exactly what we need for being 100% payrate delegate +5% +5% +5%
-
Fantastic work, this is exactly what we need for being 100% payrate delegate +5% +5% +5%
I don't see that they've proposed a delegate (?) Are you suggesting that they should?
-
CONGRATULATIONS ! +5%
I'll give it a try!
-
Fantastic work, this is exactly what we need for being 100% payrate delegate +5% +5% +5%
I don't see that they've proposed a delegate (?) Are you suggesting that they should?
Absolutely. Unless they want to contribute to BTS ecosystem for free. As a matter of fact, such kind of work is very imperative for the current BTS ecosystem, because it will add a lot of value.
Also, I think the original poster is a good example for others who want to apply for high payrate delegates. Do something first and convince the community that your work is valuable and promising, and then the community will gladly vote for you.
-
Fantastic work, this is exactly what we need for being 100% payrate delegate +5% +5% +5%
I don't see that they've proposed a delegate (?) Are you suggesting that they should?
Absolutely. Unless they want to contribute to BTS ecosystem for free. As a matter of fact, such kind of work is very imperative for the current BTS ecosystem, because it will add a lot of value.
Also, I think the original poster is a good example for others who want to apply for high payrate delegates. Do something first and convince the community that your work is valuable and promising, and then the community will gladly vote for you.
I'm right there with you. Fully agree. While I like to know more about someone and what he/she/they would do as a delegate, the wallet app is an impressive step.
-
Thanks everyone for the responses and suggestions.
@xeroc, sending to a blockchain registered name is on the TODO list. (also scan pubkey and scan privkey to load paper wallets)
@arhag,
"Does the Android client validate that the transaction to be signed returned by the server is one which sends X BitUSD to Y address where X and Y are the same as the one displayed in the confirmation to the user"
No we don't, its on our TODO list.
We plan to use Bitshares-JS transaction parsing to verify that the transaction digest (that the server is giving us to sign) is valid.
(And the destination address are the ones we choose)
"Do you plan to allow the server to create and the client to sign (and ideally partially validate) an outgoing transaction to a TITAN address?"
Yes, we plan to do that.
"Do you plan to support multisig addresses like 2-of-3 where one of the keys is held by the server and the server only signs the transaction after verifying the real user's intent with two-factor authentication?"
No at the moment, but maybe in the future.
Things that we have on our TODO list.
- add localization framework
- fix known bugs
- Security review by Sergio (and/or others)
- Usable iOS version
- Scan privkey/public key
- Send to a registered name. (Public key and TITAN transfer)
- Register your account
- Load/Unload with BTC
- Load/Unload with ARS
I would like to know what the community thinks is a reasonable payrate (and the duration) to help us in the development of the wallet.
-
Thanks everyone for the responses and suggestions.
@xeroc, sending to a blockchain registered name is on the TODO list. (also scan pubkey and scan privkey to load paper wallets)
@arhag,
"Does the Android client validate that the transaction to be signed returned by the server is one which sends X BitUSD to Y address where X and Y are the same as the one displayed in the confirmation to the user"
No we don't, its on our TODO list.
We plan to use Bitshares-JS transaction parsing to verify that the transaction digest (that the server is giving us to sign) is valid.
(And the destination address are the ones we choose)
"Do you plan to allow the server to create and the client to sign (and ideally partially validate) an outgoing transaction to a TITAN address?"
Yes, we plan to do that.
"Do you plan to support multisig addresses like 2-of-3 where one of the keys is held by the server and the server only signs the transaction after verifying the real user's intent with two-factor authentication?"
No at the moment, but maybe in the future.
Things that we have on our TODO list.
- add localization framework
- fix known bugs
- Security review by Sergio (and/or others)
- Usable iOS version
- Scan privkey/public key
- Send to a registered name. (Public key and TITAN transfer)
- Register your account
- Load/Unload with BTC
- Load/Unload with ARS
I would like to know what the community thinks is a reasonable payrate (and the duration) to help us in the development of the wallet.
100% pay is good for now.
-
100% pay rate for now +5%
-
Even if the wallet cannot receive stealth transactions (since it cannot scan the blockchain), can it still create transactions to stealth addresses so it can send to titan names? (or will it be possible in the future)
Also, does the protocol allow to register a single normal address on the blockchain with a name, so people can still use titan names to send to you (so you keep the convenience but dont have the stealth address aspect)?
Typing in a name is just sooo much more convenient than keeping track of long alphanumeric strings, so I really hope it can also be done on mobile clients.
Btw so happy to see this! It seriously made my day that there's already a functional mobile wallet prototype, especially when we thought we didn't even have any developers working on it just a short while back. I hope this gets open sourced and funded by a delegate, I will definitely vote for a 100% paid delegate. Bitwallet could become the bitshares flagship mobile wallet.
-
100% pay is good for now.
100% pay rate for now +5%
This^^^^
-
I would vote for you at 100% payrate. Let us know what your delegate name is.
-
This is just AWESOME news!
And in Argentina! Even better!
+5% +5% +5%
On the delegate thing - make it ASAP at 100% pay rate , you have my vote (and other peoples too I assume) !
-
Even if the wallet cannot receive stealth transactions (since it cannot scan the blockchain), can it still create transactions to stealth addresses so it can send to titan names? (or will it be possible in the future)
Also, does the protocol allow to register a single normal address on the blockchain with a name, so people can still use titan names to send to you (so you keep the convenience but dont have the stealth address aspect)?
Typing in a name is just sooo much more convenient than keeping track of long alphanumeric strings, so I really hope it can also be done on mobile clients.
Btw so happy to see this! It seriously made my day that there's already a functional mobile wallet prototype, especially when we thought we didn't even have any developers working on it just a short while back. I hope this gets open sourced and funded by a delegate, I will definitely vote for a 100% paid delegate. Bitwallet could become the bitshares flagship mobile wallet.
Yes open source is preferred IMHO.
Anyway, good job so far!
-
How do i send money to the wallet?
Select and address from the "My Addresses" list and use the wallet_transfer_asset_to_address command from the console (in the desktop wallet).
e.g.: wallet_transfer_asset_to_address USD 5 my_account BTSX9pTBfYkFwmUm46XTaeTLukGDrupobHwzc
should be:
wallet_transfer_asset_to_address 5 USD my_account BTSX9pTBfYkFwmUm46XTaeTLukGDrupobHwzc
-
I will vote for your 100% delegate.
Please focus on the Moblie wallet...
:)
-
Good job!
I can provide Italian translations if needed. Also for other projects.
Let me know.
-
How do i send money to the wallet?
Select and address from the "My Addresses" list and use the wallet_transfer_asset_to_address command from the console (in the desktop wallet).
e.g.: wallet_transfer_asset_to_address USD 5 my_account BTSX9pTBfYkFwmUm46XTaeTLukGDrupobHwzc
should be:
wallet_transfer_asset_to_address 5 USD my_account BTSX9pTBfYkFwmUm46XTaeTLukGDrupobHwzc
那篇中文翻译也改下吧
translate: please edit the translation post as well.
-
Will vote 100% delegate in too ;)
Great work!
-
Fantastic work, this is exactly what we need for being 100% payrate delegate +5% +5% +5%
I don't see that they've proposed a delegate (?) Are you suggesting that they should?
Absolutely. Unless they want to contribute to BTS ecosystem for free. As a matter of fact, such kind of work is very imperative for the current BTS ecosystem, because it will add a lot of value.
Also, I think the original poster is a good example for others who want to apply for high payrate delegates. Do something first and convince the community that your work is valuable and promising, and then the community will gladly vote for you.
+5
Sent from my ALCATEL ONE TOUCH 997D
-
How do i send money to the wallet?
Select and address from the "My Addresses" list and use the wallet_transfer_asset_to_address command from the console (in the desktop wallet).
e.g.: wallet_transfer_asset_to_address USD 5 my_account BTSX9pTBfYkFwmUm46XTaeTLukGDrupobHwzc
should be:
wallet_transfer_asset_to_address 5 USD my_account BTSX9pTBfYkFwmUm46XTaeTLukGDrupobHwzc
Updated
-
@ElMato I'm curious as to the reasons for developing this in Javascript as opposed to making a native app in Java. Did you consider doing that but found it was too complicated? Did you build on the work done by jcalfee on Bitshares-JS?
-
Will vote 100% delegate in too ;)
Great work!
+1
This is much needed!
Sent from my iPhone using Tapatalk
-
@ElMato I'm curious as to the reasons for developing this in Javascript as opposed to making a native app in Java. Did you consider doing that but found it was too complicated? Did you build on the work done by jcalfee on Bitshares-JS?
@svk, despite the fact that the wallet is not a complex app, but as you may know having two (or three) different codebases to support different platforms (iOS/Android/Other) would have taken us more time to have something up and running.
My personal preference is of native apps over hybrid ones, but i have to admit that for phones released in the last 2/3 years the performance is quite acceptable for these last ones and this will only get better over time.
In the cases where the JS-engine (as we are experiencing in iOS) is not able to perform well, we write a native plugin.
-
We have a working TITAN transfer. It needs to download transactions and use unspent balances ( which you can know by summing or you can cheat and check the api with the balance Id ). Also TITAN generates extra data like the latest account HD key index and the trx that needs to go into a wallet backup. It is not so easy, but good news it is on my list of things to do for the end of the year! It would be a good start to have a nice automated backup to a service like Dropbox. You're wallet will be very helpful! Thank you.
https://github.com/BitShares/BitShares-JS/blob/master/scratchpad/trx.coffee
-
@ElMato I'm curious as to the reasons for developing this in Javascript as opposed to making a native app in Java. Did you consider doing that but found it was too complicated? Did you build on the work done by jcalfee on Bitshares-JS?
@svk, despite the fact that the wallet is not a complex app, but as you may know having two (or three) different codebases to support different platforms (iOS/Android/Other) would have taken us more time to have something up and running.
My personal preference is of native apps over hybrid ones, but i have to admit that for phones released in the last 2/3 years the performance is quite acceptable for these last ones and this will only get better over time.
In the cases where the JS-engine (as we are experiencing in iOS) is not able to perform well, we write a native plugin.
Thanks for your reply, that makes sense of course, I keep forgetting there's such a thing as iOS ;)
-
An update on my lost 1.10$ .. I actually haven't lost them .. they just didn't appear in the "history" ..
-
An update on my lost 1.10$ .. I actually haven't lost them .. they just didn't appear in the "history" ..
I thought I have the same problem, but it was that the wallet took a minute to load the funds.
-
An update on my lost 1.10$ .. I actually haven't lost them .. they just didn't appear in the "history" ..
@xeroc, they didn't appear in the desktop wallet history or in the mobile wallet?
-
An update on my lost 1.10$ .. I actually haven't lost them .. they just didn't appear in the "history" ..
@xeroc, they didn't appear in the desktop wallet history or in the mobile wallet?
Desktop wallet .. devs already know about it
-
Send/receive buttons disappear in android 5.0 (nexus 5)
Need to be tested on the latest version.
-
Thanks for the feedback clayop, we never tested on android 5.0.
We have a new version coming out, i will test on 5.0.
-
May I ask when the IOS version come out?many thanks!
-
May I ask when the IOS version come out?many thanks!
+1
Happy to help test iOS
-
I have updated the OP with the instructions to upgrade to alpha-2 version.
* Backup wallet
* Install new version
* Restore wallet
Screenshots and apk
https://www.dropbox.com/sh/0xfnkep3u1dvjmt/AABVmvgXx3tb2mf3QqAj8yBKa?dl=0
* i18N ready (english and spanish available)
* Send to registered name (non-TITAN)
* Scan publickey
* Scan paper wallet
* Multicurrency CNY/USD/BTC/Gold
* Local address book
iOS version is coming soon (@dargonar is now testing it), if you want to help us test, please provide us with your device id.
We have developed a cordova plugin to do all the crypto stuff.
https://github.com/latincoin-com/cordova-plugin-bitwallet
I also want to let you know that we are running a campaign for a 100% pay delegate to help us fund the development.
So if you are interested please vote elmato. !!!
https://bitsharestalk.org/index.php?topic=12494.0
-
...
* i18N ready (english and spanish available)
...
Russian i18N pull request: https://github.com/latincoin-com/bitwallet/pull/2
-
...
* i18N ready (english and spanish available)
...
Russian i18N pull request: https://github.com/latincoin-com/bitwallet/pull/2
Merged, tested and APK rebuilt.
Thanks testz!
-
...
* i18N ready (english and spanish available)
...
Russian i18N pull request: https://github.com/latincoin-com/bitwallet/pull/2
Merged, tested and APK rebuilt.
Thanks testz!
Enjoy! :) Let's us know if you need more translations.
-
I pulled request about Korean translation ;)
https://github.com/latincoin-com/bitwallet/pull/3
-
"Unable to refresh" when launching the app. Also cannot receive fund (or just not shown).
Nexus 5, android 5.0.1
-
I pulled request about Korean translation ;)
https://github.com/latincoin-com/bitwallet/pull/3
Tested and merged. (APK rebuilt)
Thanks clayop!
-
I pulled request about Korean translation ;)
https://github.com/latincoin-com/bitwallet/pull/3
Tested and merged. (APK rebuilt)
Thanks clayop!
You're welcome :D
-
"Unable to refresh" when launching the app. Also cannot receive fund (or just not shown).
Nexus 5, android 5.0.1
Did you follow the instructions to update?
(export wallet, install, import wallet)
You can always view your balance using.
https://bsw.latincoin.com/api/v1/addrs/[your address here]/balance
-
"Unable to refresh" when launching the app. Also cannot receive fund (or just not shown).
Nexus 5, android 5.0.1
Did you follow the instructions to update?
(export wallet, install, import wallet)
You can always view your balance using.
https://bsw.latincoin.com/api/v1/addrs/[your address here]/balance
Hmm I just installed alpha 2. Do I have to install alpha1 first?
-
No, you don't.
But did you have alpha-1 installed?
-
No, you don't.
But did you have alpha-1 installed?
Oh now I can remember I did. I installed alpha 1 and uninstalled then.
-
Ok, if you never have used the wallet (transfer bitXXX from desktop wallet to mobile) there's no problem.
Did you transfer bitAssets to the old wallet? or to this one?
-
Ok, if you never have used the wallet (transfer bitXXX from desktop wallet to mobile) there's no problem.
Did you transfer bitAssets to the old wallet? or to this one?
No I never used alpha 1 wallet... just looked around it.
I sent to new one, and I PMed you :)
-
It would be great if the desktop client would show a QR code so we can scan it with the mobile wallet and have the addy.
Any chance the mobile wallet will support typing in a registered account name?
-
* i18N ready.
- english
- spanish
- russian [thanks testz]
- korean [thanks clayop]
- chinese [thanks btswildpig]
Thanks for your effort. While the i18n support is ready, many of us still cannot have cihnese interface. Could you please add a menu that users can choose the language they want? Thanks
-
Sure, but could you please first re-download the apk and verify that the shasum is ec4ff1bd9d5a44d7a212029dcd1bebd153fa2395?
This is what i see when i switch my phone to chinese.
http://cl.ly/image/1A3g360C3h0C
-
Sure, but could you please first re-download the apk and verify that the shasum is ec4ff1bd9d5a44d7a212029dcd1bebd153fa2395?
This is what i see when i switch my phone to chinese.
http://cl.ly/image/1A3g360C3h0C
the new version works. thanks a lot!!
-
I have updated the OP mainly to warning testers to not fund the mobile wallet using the GUI.
We should use wallet_transfer_to_address, otherwise the GUI will generate a titan transaction that wont be visible to the mobile wallet (for now).
If it happens by mistake PM me and i will help you recover those funds.
-
Will it be possible to also integrate the faucet for free name registration in the mobile wallet?
-
Pull request for italian translation:
https://github.com/latincoin-com/bitwallet/pull/8
-
This is looking great!
Any plans in the pipe for an iOS version?
-
@Rune in the beta version you will be able to register your name as soon as you install the app. @dargonar is working on it right now.
@spartako, tante grazie per la traduzione la abbiamo già aggiunta!!
@mdj, iOS version is working fine. If you want to help us test PM you device UUID or go to https://github.com/latincoin-com/bitwallet/tree/dargon-dev-ios and build it yourself!
-
@spartako, tante grazie per la traduzione la abbiamo già aggiunta!!
Grazie per il vostro fantastico lavoro!! ;)
-
@Rune in the beta version you will be able to register your name as soon as you install the app. @dargonar is working on it right now.
Sounds great, is the free registration through faucet.bitshares.org?
Also do you have any ideas for how to link identities in the future? Users will want to have the same hot account on both their laptop and their phone. I was thinking maybe simply sharing private keys by scanning a QR code on the windows client. But I guess there's an even bigger issue that it's difficult to sync between several clients.
Maybe you could simply register separate names under the same top level name for each device, like laptop.username, mobile.username, coldwallet.username. Then they could have separate keys but stay unified for bitshares login. I actually like this also because it would make for excellent 2 FA security if you have a multisig address that requires signature from both laptop.username and mobile.username.
There was a discussion about how mobile/laptop clients would sync for bitshares login in the thread on reddit and I've been thinking about it since because it's an area where all other local authentication systems have failed in the past, including bitID.
-
https://github.com/latincoin-com/bitwallet
Could someone from german section help to translate mobile wallet ... this would be really great +5%
-
https://github.com/latincoin-com/bitwallet
Could someone from german section help to translate mobile wallet ... this would be really great +5%
if you point me to the folder i have to look i will try
-
https://github.com/latincoin-com/bitwallet/tree/master/www/static
https://github.com/latincoin-com/bitwallet/pull/8
you can check here if there are more files to go
-
https://github.com/latincoin-com/bitwallet/tree/master/www/static
https://github.com/latincoin-com/bitwallet/pull/8
you can check here if there are more files to go
can you create the german file? i tried, but i think i messed up. Hope nothing bad happend to the english file.
-
It's git, you don't have to worry ;)
-
is there a opportunity to get the screen design as ai/svg/eps/psd or whatever?
This would be awesome :)
-
why is elmato still not an elected delegate? join me in voting for him.
-
another reason for a mobile wallet https://bitsharestalk.org/index.php?topic=12761.msg167986#msg167986
-
why is elmato still not an elected delegate? join me in voting for him.
I've joined you. Others should as well.
-
Hi everyone, we are getting back from the new year holidays, i wish everyone here a happy 2015.
Im posting to update everyone were we are at the moment.
- Delegate election.
I want to thank everyone who has voted so far, we are in the middle (~3.6% -> 7.5% to position 101) of the necessary votes to being elected and if you haven't voted yet you can do it now!
(BTW: is there a simple tutorial on how to vote?, something like http://bytemaster.bitshares.org/tutorial/2015/01/03/How-to-Register-a-BitShares-Account/ ?)
- What we have done before new year.
* We have moved all the crypto stuff from JS to "native" (with a cordova plugin), the performance gain has been notable in Android.
https://github.com/latincoin-com/cordova-plugin-bitwallet
* We started to use the latest version of the UI framework that (i hope) will enhance the experience thanks to the improvements in view transition and caching system.
- What are we working now.
* Moving to latest UI framework.
* Backend infrastructure for BTC <-> bitUSD
* User account registration.
- What is next.
* Design / Usability / Navigation improvements.
* Backend optimization (using new api call from bitshares daemon)
(I have a pending task that its o make the roadmap available for everyone to see)
- iOS testing
We will be using testflightapp.com to test the iOS version, so if you want to help us test follow the instructions in this link.
http://tflig.ht/1vUyctu
-
- iOS testing
We will be using testflightapp.com to test the iOS version, so if you want to help us test follow the instructions in this link.
http://tflig.ht/1vUyctu
Just requested access to the beta. Is this a live functioning app, with real funds?
-
- iOS testing
We will be using testflightapp.com to test the iOS version, so if you want to help us test follow the instructions in this link.
http://tflig.ht/1vUyctu
Just requested access to the beta. Is this a live functioning app, with real funds?
Yes it is, its an alpha version, so don't put significants amount of money in it.
-
@Rune in the beta version you will be able to register your name as soon as you install the app. @dargonar is working on it right now.
Sounds great, is the free registration through faucet.bitshares.org?
Also do you have any ideas for how to link identities in the future? Users will want to have the same hot account on both their laptop and their phone. I was thinking maybe simply sharing private keys by scanning a QR code on the windows client. But I guess there's an even bigger issue that it's difficult to sync between several clients.
Maybe you could simply register separate names under the same top level name for each device, like laptop.username, mobile.username, coldwallet.username. Then they could have separate keys but stay unified for bitshares login. I actually like this also because it would make for excellent 2 FA security if you have a multisig address that requires signature from both laptop.username and mobile.username.
There was a discussion about how mobile/laptop clients would sync for bitshares login in the thread on reddit and I've been thinking about it since because it's an area where all other local authentication systems have failed in the past, including bitID.
No, the registration wont go through faucet.bitshares.org.
We will pay it from our own BTS funds.
- Regarding identities, login, wallets, etc.
We also have in mind the "scan private key" to load your identity in the mobile wallet.
But as you know, the wallet isn't just the identity of the user.
The wallet keep track of many things.
- Unspent balances.
- Destination names of TXs you have made.
- Etc, etc.
The ideal approach (ideal != best) will be to have something like Ripple's Blob Vault (+reliable, +distributed).
Then, with your identity (signature) you get all your wallet information that is stored encrypted.
But the software wallet has to sync it every time there is a change …
We need to think more about this … but for the time being we will let to the user the responsibility to backup his wallet. (We will do automatic backup [as the desktop wallet], but the user need to upload it to a safe place or backup to his dropbox/gdrive folder)
-
I'm sorry if this is answered elsewhere, but does this run a full node on the phone? Or is this using light-wallet functionality?
-
I'm sorry if this is answered elsewhere, but does this run a full node on the phone? Or is this using light-wallet functionality?
your phone holds the privkeys and signs transactions the rest is on a central server ...
-
How much trust is involved with using a central server? What kind of vulnerabilities are exposed with this?
-
He could simply deny to forward your tx ... thats about it .. but i havent check the sources
-
How much trust is involved with using a central server? What kind of vulnerabilities are exposed with this?
He's basically running an api server. Unless the wallet itself is malware and sends him the private keys all the server is doing is processing signed and encrypted transactions.
Brilliant.
Sent from my Timex Sinclair
-
When will this officially be released on the actual App Store? I assume sometime after the Bitshares 1.0 release?
-
When will this officially be released on the actual App Store? I assume sometime after the Bitshares 1.0 release?
+5%
-
How much trust is involved with using a central server? What kind of vulnerabilities are exposed with this?
He's basically running an api server. Unless the wallet itself is malware and sends him the private keys all the server is doing is processing signed and encrypted transactions.
Brilliant.
Sent from my Timex Sinclair
@fluxer555 i find your concerns very important because those are the same questions i ask before using any kind of wallet.
So let me explain a little more how the wallet works.
As far as i know, every BitShares lightweight client will need the assistance of a central server.
The alternative will be to implement something like this
https://blog.ethereum.org/2015/01/10/light-clients-proof-stake/
in the core.
Mobile wallet
1) The first time the client runs private keys are generated in the phone.
(in Android we use bitcoinj => SecureRandom [with PRNGFixes], basically /dev/urandom)
(in iOS we are using CoreBitcoin => /dev/random)
2) Every time the client wants to make a transaction he asks the server something like this.
- I want to transfer 10 USD from A,B,C to Z
3) The server returns an UNSIGNED transaction [1] that fulfills the client requirement (10 USD to Z)
4) The client using his local private keys signs the transaction, and ask the server to forward it to the network.
This is the basic usage.
[1] The client is NOT validating yet that the transaction built by the server is in fact what i asked the server to do.
If the server is compromised and we have [1] resolved, there is no much harm that an attacker could possible do in terms of stolen funds. (Of course it will disrupt normal operation)
The code is open, so you can take a look at it and build your own binaries if you don't trust ours!
-
Thank you ElMato. So until [1] is resolved, there is a potential for a 'man-in-the-middle' attack? What vulnerability is there without [1] resolved?
-
Thank you ElMato. So until [1] is resolved, there is a potential for a 'man-in-the-middle' attack? What vulnerability is there without [1] resolved?
No, MITM attacks are not possible since we are talking with an https service.
Put in another way, we have the same risk as a the Coinbase wallet.
The vulnerability until [1] is resolved will only arise if our api server is compromised.
But even in that case the attacker can't steal your private keys, he can only modify the destination of your transaction.
Remember the server doesn't know about your private keys, he only knows your public keys.
[1] will be soon added to the client.
-
Yahhman your android wallet is working great on my device. Nice work!
I'd love to see a Mycellium-like Exchange feature where we can post meetup offers to exchange BTS or bitUSD for cash. Bitshares P2P gateway to/from cash in your pocket. ;)
-
Yahhman your android wallet is working great on my device. Nice work!
I'd love to see a Mycellium-like Exchange feature where we can post meetup offers to exchange BTS or bitUSD for cash. Bitshares P2P gateway to/from cash in your pocket. ;)
This would be super sweet.
How far down are the long term plans full decentralized exchange functionality? I guess implementing that won't be so simple, but trading directly on the phone would be pretty neat though.
-
No, MITM attacks are not possible since we are talking with an https service.
Put in another way, we have the same risk as a the Coinbase wallet.
The vulnerability until [1] is resolved will only arise if our api server is compromised.
But even in that case the attacker can't steal your private keys, he can only modify the destination of your transaction.
Remember the server doesn't know about your private keys, he only knows your public keys.
[1] will be soon added to the client.
What's stopping a compromised central server from sending false validation back to the wallet?
-
I am very excited about the BitUSD wallet.
When do you think we can expect it to launch?
(I want to build a funnel with a coming soon page, collect emails and then notify them as soon as it is released)
-
@rgcrypto, we are aiming for mid-february.
-
@rgcrypto, we are aiming for mid-february.
Will you support TITAN?
-
No for the mid Feb release.
We plan to support it later when the mail subsystem is well tested. Anyway you will have some level of privacy choosing from which balances you want to spend and to which balance you want to receive.
-
Please give me your input on this Mobile Wallet Coming soon page.
Let me know if it is ready to go.
http://bit.ly/BitUSD-Wallet
PS: People will be able to use their affiliate ?r= on this funnel and the email will be available in the future for anything related to BitUSD project.
-
What's stopping a compromised central server from sending false validation back to the wallet?
Still waiting for an answer to this. Also, what will the wallet do if the transaction does not validate? At that point, it is too late, right?
-
@fluxer555, i think i've already answered your question.
But lets do it again.
The task for the server is to build transactions based on what the client asked to do and relay them to the network after the client signs it.
So, there is no such thing as "false validation".
If an attacker compromise our server and we don't have [1] implemented, the attacker can create a malicious transaction (changing the destination of the funds) then the client will sign (without validating) and funds will be lost.
If the transactions does not validate, the client won't sign it, so no funds lost.
Is this answer enough? or you need more clarifications?
-
are there any updates on this?
-
[1] The client is NOT validating yet that the transaction built by the server is in fact what i asked the server to do.
If the server is compromised and we have [1] resolved, there is no much harm that an attacker could possible do in terms of stolen funds.
So, there is no such thing as "false validation".
If an attacker compromise our server and we don't have [1] implemented, the attacker can create a malicious transaction (changing the destination of the funds) then the client will sign (without validating) and funds will be lost.
If the transactions does not validate, the client won't sign it, so no funds lost.
I just want to clarify that even with [1] resolved, a user can still lose money if the server is compromised.
One method is to change the active key reported by the server for a given account name. The client has no way of knowing the mapping between human-readable account name to active public key. That would require the client to download and process the full blockchain which is not feasible for a mobile client.
Alternatively, we could take some notes from Ethereum and augment our consensus system to use a Merkle Patricia tree to represent the state of the entire database in periodic snapshots, commit the root hash of that database snapshot into the block headers, and have a super majority of the delegates confirm that snapshot as part of their block signing process, as I described here (https://bitsharestalk.org/index.php?&topic=13965.msg182455#msg182455); that coupled with further changes in block production procedure that make it possible for lightweight clients to update the set of active delegates (https://bitsharestalk.org/index.php?topic=13940.0) over time with minimal trust assuming they do not resync too infrequently, means that a lightweight client could verify proof of the existence of some state in the database (where the proof scales logarithmically with the number of keys in the database) in a very low trust manner. But that requires a lot of complicated changes and work, so we can't expect that anytime soon.
There is a much simpler way to protect against this threat however. First, would be to use the TOFU (trust on first use) security principle. The mobile wallet could automatically add to the contacts list any account name to whom the user sends funds. The mobile wallet would log the association between the account name and the owner/active public keys. If the active public key changes, the mobile wallet would require proof (the transaction signed by the owner key that changed the active key) from the server in order to update its local active public key associated with the account. If the server ever sends the mobile wallet an unsigned transaction where the active public key or owner public key associated to an account name that the user wants to send funds to is not the one stored in the local database of the mobile wallet, it would warn the user that the server is likely compromised and explain to the user how to proceed. Second, it should also be possible for the user to pin a contact as trusted (which would show up in the GUI in a special way when sending that account funds). Pinning a contact as trusted means that the user has manually verified the owner key of the account through out-of-band methods and trusts that is it correct (it could also mean that pinned accounts will keep their associated owner/active public key in the local database and that data cannot be garbage collected to save space like it could be possible with the auto-added contacts). A user may be more careful about sending funds to an unpinned account than a pinned account. For example, if they want to send a large amount of money to some unpinned account, they might first send a small amount, verify through outside channels (like in person or over the phone) that they received the payment, pin the account, and then send the rest of the larger sum of money.
The other method by which the user can lose money is through the server making it appear as if the user received funds (very similar to a double-spend attack). The attacker that compromised the server (say they were able to get the server's private SSL keys and man-in-the-middle or rather man-on-the-side attack the user's connection) could buy goods/services from the user (or exchange cryptocurrency for cash or other cryptocurrency) and make it appear as if the user received funds for the exchange. For example, the attacker could send a legitimate (properly signed) transaction to the user's address that was funded by withdrawing funds from an illegitimate balance (a balance that does not exist or does but has 0 funds in it). Without the Merkle Patricia tree discussed above, the user is forced to trust the server about the existence of balances in the consensus database.
Unfortunately there is no way to protect against this attack without the complex improvements to lightweight client validation that I discussed above. Fortunately, it is fairly difficult to pull off since it requires not just compromising the server but also compromising the specific victim (and the victim's internet connection) in a live environment usually with physical presence required by the attacker's agents (to actually buy the good/service in person). Also, the typical victim (a merchant) would usually be someone who is capable of running a full client.
Finally, this is not bringing up all of the other possible attacks that become possible when you want to move beyond simply transferring assets to other parties. For example, a light wallet that was capable of trading on the DEX would be very vulnerable to the server. The server could make the order book appear to the user in anyway it wanted. Fortunately, if it is too strange the user will become suspicious of the server, since the prices can only deviate from what user expects them to be so far before the user attempts to verify through other means. Still, small tweaks to the order book could allow the server to profit immensely by front running its users.
-
Hi everyone, here is a quick update to keep the community posted.
We (Pablo and I) are working hard to get our third release ready as soon as possible.
There has been a lot of changes going in the backs that are helping us to test while we develop.
Since want to give our users a clean/fast/integrated experience on the wallet, we developed and auto exchange for bitUSD/bitCNY <-> BTC
This auto exchanger will help us provide our first deposit/withdraw method inside the app.
(NOTE: We know that there are alternatives to this [shapeshift, metaexchanger and alt's gateway], and we keep an eye on them to integrate in the future)
Besides the "$15 sent to Pablo", "$12 received from Matias" type of transactions, we want the users to view something like this on the main screen.
"$250 Deposited"
"$200 Withdrawn"
"0.05 BTC sent to XXX ($11.04 USD)"
The auto exchanger works with two api calls.
Example : I want to "Deposit" 5 USD paying in BTC.
GET https://bsw-test.latincoin.com/api/v1/buy/USD_BTC/5
{
"quote": {
"client_pay": "0.02230252 BTC",
"timestamp": "1423504598",
"rate": "224.18991218",
"client_recv": "5.00 USD"
},
"signature": "c495550ef134d00ec21889660772877952afc74878d3add28f2143086ae14295"
}
If you accept the quote you need to POST the quote back to the server with your desired destination address and your previously generated token.
POST https://bsw-test.latincoin.com/api/v1/accept
{
"quote": {
"client_pay": "0.02230252 BTC",
"timestamp": "1423504598",
"rate": "224.18991218",
"client_recv": "5.00 USD"
},
"destination_address" : "DVS6KBKUMcWXvgY7c9sYqHv4p47baAn6NBPR",
"signature": "c495550ef134d00ec21889660772877952afc74878d3add28f2143086ae14295",
"token" : "66ecd0a1f222f3edfce79615896cfc91ecb6487af0d00a6cf2ca9d41cb96d32f"
}
After that a transaction will be generated waiting for the payment to be made.
{
"tx": {
"status": "WP",
"rate": "224.18991218",
"cl_recv_curr": "USD",
"quoted_at": "1423504598",
"cl_recv_addr": "DVS6KBKUMcWXvgY7c9sYqHv4p47baAn6NBPR",
"cl_recv": "5.00000000",
"cl_pay": "0.02230252",
"id": 126,
"cl_pay_curr": "BTC",
"cl_pay_addr": "BxMU8x3EU1mF2kNan4fyCwu7MhWNPAPjRY"
}
}
The token is obtained after a signup process with the server.
GET https://bsw-test.latincoin.com/api/v1/signup
{
"msg": "SignMePlease|c90355493833bfa8f739923f7f83d550063d0aa2d943cae8f0f88c11af771b99|1423505360|513424133231708f60bfffdeff9cf9929f35741f6318d4887929667e935d6cec",
"signature": "1f7925047f1d26c435bd38e88c2c018c74528b229836df40f19be046649ba41884771a2cc7951f684760f654c9b824cf8018bc89092acf84937b7723ebae6a2304"
}
"signature" is the signature of "msg" from the server in order to identify the service.
Then you have to sign "msg" with your private key and POST back to the server.
POST
{"message": "SignMePlease|c90355493833bfa8f739923f7f83d550063d0aa2d943cae8f0f88c11af771b99|1423505360|513424133231708f60bfffdeff9cf9929f35741f6318d4887929667e935d6cec", "pubkey": "DVS7uY73UseX7JVGVzQwiuQ14Z82PtjtGin8AgvSfYtY1gUrFVhVx", "signature": "2013d56e7714b17799948daf7a7353821f58e3bc61d9f50c649efdb7de718d55101ece52f616495c3a1b9ebb0a22ff952daafc6833bba03214268f0a0296ec6663"}
And a token will be generated.
{"token": "66ecd0a1f222f3edfce79615896cfc91ecb6487af0d00a6cf2ca9d41cb96d32f"}
This is a raw/ugly screen flow for the third release to have a preview of what you can expect in the next version.
(http://i.imgur.com/hUodEQvm.jpg)
http://imgur.com/hUodEQv
Texts and GUI Elements are not final so don't worry about it.
Our third release will have the same "basic" UI design and for the next release
@cass will be helping us with the UI.
-
One method is to change the active key reported by the server for a given account name. The client has no way of knowing the mapping between human-readable account name to active public key. That would require the client to download and process the full blockchain which is not feasible for a mobile client.
@arhag you are right.
One method to avoid this kind of attack is to allow the user to share his account (name+pubkey) information through another channel (whatsapp? mail? ) . Then the wallet can add that contact information directly from the other party.
-
WIll the GUI support account names instead of pub keys? the QR codes will be generated based on registered bitshares account name and not pub keys right?
-
One method to avoid this kind of attack is to allow the user to share his account (name+pubkey) information through another channel (whatsapp? mail? ) . Then the wallet can add that contact information directly from the other party.
Yes. Also, I think it would be really nice if you could use the mobile wallet to easily exchange that information directly in person (maybe with QR code or Bluetooth or NFC?).
http://imgur.com/hUodEQv.
Wow. This is really exciting. I didn't think you would have Bitcoin deposit and withdraw features (with automatic conversion through a bridging service) anytime soon in the mobile wallet. Since that means you must be running a Bitcoin node on the server as well, what are your thoughts on allowing the mobile wallet to act as a Bitcoin wallet as well (and augment the API with the server to receive and create Bitcoin transactions)?
-
WIll the GUI support account names instead of pub keys? the QR codes will be generated based on registered bitshares account name and not pub keys right?
@jsidhu yes the wallet will support account names and QR codes will be generated based on that names (if the user has his account registered).
-
bitcoin bridge support is AMAZING. Nullstreet was literally in the middle of a discussion about "when is someone gonna make this so we have something to market".
Awesome!!!!!!!!!
Hope it'll be ready soon, this should what our ads are focusing on.
edit: it's meant to be able to send and receive bitcoin just like a regular bitcoin wallet (scanning/generating bitcoin QR codes), right? Ideally it should be able to scan a bitpay QR code and get the address and amount, then send the amount to the bridge to get a locked in quote for an amount that corresponds to the price of the locked in bitpay quote, and then have the bridge return the amount of bitUSD the wallets need to send to the bridge account with a memo that makes the bridge return any funds that are in excess of the quote, and return all funds if they are below the quote.
-
When this is produced, I will concentrate all my effort on promoting your wallet. I might change the youtube channel to bitwallet.tv lol. This is everything. This is what we can get on millions of phones. This is how we can get bitUSD in millions of hands. This is how we increase bitUSD volume and make every exchange on the planet beg to integrate us. this is how we get a shit tonne of free press. This is how we get Andreas Antonopolos, Roger Ver, Barry Silbert, and every other pundit mentioning us on every television interview. This is orders of magnitude more important than any other bitshares project. Once done all of the other ideas will work. Without this first, none of the other ideas will work.
Just make sure it is technically tight. Don't leave room for hackers of any kind.
All by doing something as easy as following the first rule of business. "If you help enough people get what they want, you can everything you want."
-
I agree that the mobile wallet with the ability to hold bitcoin is very important. I know important things are being done on the bitshares code right now, but that's impossible to market. Checking the github for progress is depressing because it seems like tasks take so long to accomplish. Even worse is seeing extra full weeks being added on to each release date. Come to think of it the github is almost like "Anitmarketing", it only dissapoints. It would be nice if the marketing team had something usable and tangible for non-geeks to experience.
-
This is how we get Andreas Antonopolos, Roger Ver, Barry Silbert, and every other pundit mentioning us on every television interview. This is orders of magnitude more important than any other bitshares project. Once done all of the other ideas will work.
+5%
-
Fantastic work. Really looking forward to this release.
Edit: I know I'm getting ahead of myself... but any plans for an iOS version?
-
@Elmato
Are there additional resources from the community that you need to be successful?
-
I agree that the mobile wallet with the ability to hold bitcoin is very important. I know important things are being done on the bitshares code right now, but that's impossible to market. Checking the github for progress is depressing because it seems like tasks take so long to accomplish. Even worse is seeing extra full weeks being added on to each release date. Come to think of it the github is almost like "Anitmarketing", it only dissapoints. It would be nice if the marketing team had something usable and tangible for non-geeks to experience.
Sometimes shorter sprints help.. and pick a day to be demo day (not release day).. to show off what you got to the community. If forcasts and estimates are not being met then shorter sprints usually solves that and they get better at predicting time for work and increasing sprint lengths over iterations. It's what we do at work and we learned the hard way but the more experienced people are usually spot on with estimates... in general under promise and over deliver.
As far as this wallet goes, im looking forward to testing it and using it in applications.
-
Awesome!!! Can't wait. This will be huge.
-
edit: it's meant to be able to send and receive bitcoin just like a regular bitcoin wallet (scanning/generating bitcoin QR codes), right? Ideally it should be able to scan a bitpay QR code and get the address and amount, then send the amount to the bridge to get a locked in quote for an amount that corresponds to the price of the locked in bitpay quote, and then have the bridge return the amount of bitUSD the wallets need to send to the bridge account with a memo that makes the bridge return any funds that are in excess of the quote, and return all funds if they are below the quote.
@Rune, the mechanics are more or less the ones that you describe but we also have a PP (Partialy Paid) state for the exchange transaction, so you can fund it in many transfers without problems.
Also whatever you send in excess you can claim it later because you are the owner of that tx.
Just make sure it is technically tight. Don't leave room for hackers of any kind.
@bitmarket, thanks for your support we take security very seriously.
Besides all of our precautions and design considerations im in talks with Sergio Lerner's company to do a full audit of the wallet.
Edit: I know I'm getting ahead of myself... but any plans for an iOS version?
@.yoshi
We are using testflight app for iOS testing, you can go here http://tflig.ht/1vUyctu (http://tflig.ht/1vUyctu)
Are there additional resources from the community that you need to be successful?
@hpenvy2, as many projects here what we need is more horse power.
What we really need now is help in the brand design, thats why we look forward to work with @cass and @rgcrypto.
Since that means you must be running a Bitcoin node on the server as well, what are your thoughts on allowing the mobile wallet to act as a Bitcoin wallet as well (and augment the API with the server to receive and create Bitcoin transactions)?
@arhag, i will try to address some of the questions that are arising.
What we are doing It is NOT a Bitcoin wallet and even if its technically feasible we don't plan to do it because from our perspective it will confuse/dilute the value proposition that bitAssets bring to the table.
We think that the best product in the crypto world are the bitAssets.
And even if we think that our early adopters will come from the crypto community they are not our final target.
We can have the bitcoin crowd on board pitching them something like "stay in cryptoland, be stable" without forcing them to change their favorite wallet.
On the other hand i strongly support the idea of forking an existing bitcoin wallet (Electrum, Andreas Schildbach, other?) and add the option to "lock(s)" the balance in bitUSD/CNY/etc.
That will be a "reloaded" version of a bitcoin wallet.
A really nice product for the bitcoin community.
I think this product could be the HedgeWallet.
Another response would be to fork Andreas Schildbach bitcoin wallet and instead of a "Locks" button add a "to bitUSD" button.
( https://medium.com/@Coinapult/electrum-locks-plugin-beta-9d8f724af19a )
But we should rely on a centralized exchange to do the conversion because we don't have cross-chain trading yet.
This will give the same value proposition as locks but with new benefits.
-
What we are doing It is NOT a Bitcoin wallet and even if its technically feasible we don't plan to do it because from our perspective it will confuse/dilute the value proposition that bitAssets bring to the table.
...
On the other hand i strongly support the idea of forking an existing bitcoin wallet (Electrum, Andreas Schildbach, other?) and add the option to "lock(s)" the balance in bitUSD/CNY/etc.
...
I think this product could be the HedgeWallet.
Alright. But I can see that the app is using the Bitcoin URI scheme. So at least could that (and perhaps alternatively Intents on Android) provide a very nice experience for coupling an already existing Bitcoin wallet to your mobile wallet? I would like to be able to go into the BItShares mobile wallet, choose deposit, select the BitAsset type and quantity, then have the wallet automatically launch (whether through Bitcoin URL scheme for iOS or Intents on Android) a Bitcoin app installed on the device with everything filled in and ready to go. It seems like you are already planning on enabled that sort of UX with your wallet, correct? Similarly, on Android, you could have the BitShares mobile wallet also register for the Bitcoin Intent (I don't think this can be done with iOS if the user already has another Bitcoin app installed, because iOS doesn't have Android's powerful Intents features) so that it can be used to pay (by clicking on a link in the browser for example) a Bitcoin address via your bridge and fund it with their BitAsset balances.
This integration with third-party Bitcoin wallets installed on the same device could provide us something really close to the HedgeWallet until the real HedgeWallet is ready.
-
@elmato: could pls send me link to android version so i could test new alpha design workflow etc!?
This would be really great! Thx
-
Apparantly coinjar released a new feature. Allowing you to hedge BTC against AUD, GBP, EUR and USD.
https://blog.coinjar.com/2015/02/10/introducing-hedged-accounts/
-
I think it could be a good idea if BitWallet became a project that primarily focused on bitcoin users. So the integrated bridge functionality became the centerpiece of the app and development would focus on getting the user experience for that as perfect as possible. So bitcoin transactions from the wallet should be as prominent and easy as bitshares transactions.
Then we could really take advantage of the fact that we have two mobile wallets, nathan hourts would be for bitshares users while bitwallet would focus on bitcoin users. Then all marketing can focus on the bitwallet at first since that's a product with large demand we can begin selling to bitcoiners as soon as it is out.
-
What we are doing It is NOT a Bitcoin wallet and even if its technically feasible we don't plan to do it because from our perspective it will confuse/dilute the value proposition that bitAssets bring to the table.
...
On the other hand i strongly support the idea of forking an existing bitcoin wallet (Electrum, Andreas Schildbach, other?) and add the option to "lock(s)" the balance in bitUSD/CNY/etc.
...
I think this product could be the HedgeWallet.
Alright. But I can see that the app is using the Bitcoin URI scheme. So at least could that (and perhaps alternatively Intents on Android) provide a very nice experience for coupling an already existing Bitcoin wallet to your mobile wallet? I would like to be able to go into the BItShares mobile wallet, choose deposit, select the BitAsset type and quantity, then have the wallet automatically launch (whether through Bitcoin URL scheme for iOS or Intents on Android) a Bitcoin app installed on the device with everything filled in and ready to go. It seems like you are already planning on enabled that sort of UX with your wallet, correct? Similarly, on Android, you could have the BitShares mobile wallet also register for the Bitcoin Intent (I don't think this can be done with iOS if the user already has another Bitcoin app installed, because iOS doesn't have Android's powerful Intents features) so that it can be used to pay (by clicking on a link in the browser for example) a Bitcoin address via your bridge and fund it with their BitAsset balances.
This integration with third-party Bitcoin wallets installed on the same device could provide us something really close to the HedgeWallet until the real HedgeWallet is ready.
If it works with the bitcoin URI scheme... how will it handle other installed bitcoin wallets?
I support what ElMato says about forking an existing bitcoin wallet source... electrum is centralized using an API i believe so I dont thinkt hat one is possible unless we backwards engineer it.. but this allows people to use an interface they are already familiar with... and maybe one day a pull request can be merged into the original codebase if the demand is high enough.
I've developed with Andreas' android wallet and know my way aroudn that one.. it shouldn't be too hard to lock into bit assets from bitcoin...
What would this HedgeWallet provide that Andreas' wallet wouldn't be able to do?
-
is the network connection model similar to mycelium which has an api running behind some network supernodes? Is the API mechanism decentralized or a central entity? In that I mean is the code open sourced? I would imagine we would have the delegates host this API so that it is as decentralized as signing blocks.
If you are keeping the API side closed like MyCelium, please state your reason for doing so.
-
If it works with the bitcoin URI scheme... how will it handle other installed bitcoin wallets?
From my limited understanding, it is a problem on iOS. You get undefined behavior if you have more than one app register the same URL scheme. But I believe with Android you can have multiple apps register it and then the user gets to choose which one of the registered apps they want to launch.
So that means the iOS version of ElMato's mobile wallet should probably not register "bitcoin:" but rather just "bts:". But I think it could launch a "bitcoin:" URL from within the BitShares mobile wallet which would then call the Bitcoin app installed on the same device (assuming one is installed). The Android version could respond to both "bitcoin:" and "bts:". So if you click on a Bitcoin payment link in a browser, you could choose to pay using your BTC from your installed Bitcoin app, or you can choose to pay using your BitAssets (via the automated bridge to BTC) from the BitShares mobile wallet.
This is obviously not an ideal UX, which is why I was a little disappointed to hear that it is not in ElMato's plans to integrate Bitcoin functionality in the mobile wallet. But that's fine, it is just an opportunity for someone else to integrate that code along with Bitcoin wallet code into HedgeWallet and market that to Bitcoiners specifically.
I've developed with Andreas' android wallet and know my way aroudn that one.. it shouldn't be too hard to lock into bit assets from bitcoin...
Great! So are you interested in taking the lead on this HedgeWallet project?
What would this HedgeWallet provide that Andreas' wallet wouldn't be able to do?
Andreas' Bitcoin Wallet is just a Bitcoin client. HedgeWallet would be a BitShares mobile client + Bitcoin mobile client integrated into one app. It would have easy UX to convert BTC balances stored with the wallet into one of the various BitAssets and back (via a bridge). It would allow you to pay Bitcoin addresses either with real BTC or from BitAsset balances via a bridge (like shapeshift, metaexchange, or maybe even ElMato's solution). It would of course also allow you to receive real BTC and to also receive and send BitAssets through the BitShares network. The bridge services would also be used to convert one BitAsset into another directly, rather than forcing the user to go through BTC as an intermediate asset.
-
This could be a bummer:
Mycelium's Bitcoin Wallet Suspended from Google Play Store:
http://www.coindesk.com/myceliums-bitcoin-wallet-suspended-google-play-store/
-
This could be a bummer:
Mycelium's Bitcoin Wallet Suspended from Google Play Store:
http://www.coindesk.com/myceliums-bitcoin-wallet-suspended-google-play-store/
WTF Google, stop pulling an Apple. At times like these I am glad Android gives the option to allow installing APKs from Unknown Sources out of the box without rooting. Still, that is not an acceptable requirement to force on regular users, so I hope this is just an error that will quickly get resolved.
-
FFunny i just spoke about mycelium yesterday and how it had a centralized api which i dont trust
-
This could be a bummer:
Mycelium's Bitcoin Wallet Suspended from Google Play Store:
http://www.coindesk.com/myceliums-bitcoin-wallet-suspended-google-play-store/
That's where integration with something like Blackphone might come in handy...
https://blackphone.ch/
-
This could be a bummer:
Mycelium's Bitcoin Wallet Suspended from Google Play Store:
http://www.coindesk.com/myceliums-bitcoin-wallet-suspended-google-play-store/
That's where integration with something like Blackphone might come in handy...
https://blackphone.ch/
i've asked them before if they would accept BTC etc. for payment - no chance at this time ...!
-
is the network connection model similar to mycelium which has an api running behind some network supernodes? Is the API mechanism decentralized or a central entity? In that I mean is the code open sourced? I would imagine we would have the delegates host this API so that it is as decentralized as signing blocks.
If you are keeping the API side closed like MyCelium, please state your reason for doing so.
Bump.. I still want an answer to this question ElMato.
-
:)
If you are keeping the API side closed like MyCelium, please state your reason for doing so.
i don't think we'll keep it closed source ..strongly guess that API will also open sourced!
Api will be public
we should think if is convenient to opensource the backend code
-
This could be a bummer:
Mycelium's Bitcoin Wallet Suspended from Google Play Store:
http://www.coindesk.com/myceliums-bitcoin-wallet-suspended-google-play-store/
http://www.reddit.com/r/Bitcoin/comments/2vro8y/mycelium_and_google_play_recap_of_what_happened/
So note to ElMato and other mobile wallet makers: don't put a donation button in your app.
-
This could be a bummer:
Mycelium's Bitcoin Wallet Suspended from Google Play Store:
http://www.coindesk.com/myceliums-bitcoin-wallet-suspended-google-play-store/
http://www.reddit.com/r/Bitcoin/comments/2vro8y/mycelium_and_google_play_recap_of_what_happened/
So note to ElMato and other mobile wallet makers: don't put a donation button in your app.
+5%
-
Hopefully this hasn't been answered somewhere in the last 12 pages :)
So I sent money to the mobile wallet with out RTFM and now the money isn't showing up. I did the following:
1) Created mobile.riverhead in the wallet.
2) Go to accounts tab in the mobile wallet and see mobile.riverhead with a BTS address under it
3) Send some bitGold to address in #2 above to test.
I can see the transaction where I sent the money but it doesn't show in the wallet.
I did a backup of the wallet and have tried to decrypt the private key into wif format so I can import it into the desktop client. However I don't know the parameters used to encrypt the backup. Anyone know them?
Thanks!
Riverhead - Mobile.n00b (not an actual address)
-
@Riverhead
* If you plan to transfer funds from desktop wallet to mobile, don't use the GUI because it will generate a titan transaction that the mobile wallet wont see. (If it happens by mistake PM me and i will help you recovering those funds)
use wallet_transfer_to_address 5 USD your_account your_address_in_mobile from console.
To decrypt the private key.
openssl enc -aes-256-cbc -in infile -out outfile -pass pass:"wallet_password_here" -d -base64
where the content of infile is the base64 encrypted key
PM and i will help you recovering those funds.
-
LONG TIME ..
>:(
-
I heard @cass has joined their team to integrate an awesome UI :)
-
Better to have more info about what's going on..
-
damn long!!!!!!
stupid 100% delegate. >:( >:( >:(
Check recent progress here: https://github.com/latincoin-com/bitwallet/commits/dargon-dev-btc
-
Dear community,
Its been a long time without updates so i will try to summarize what we were doing and were we are going.
I was holding the update because we are pretty close to the release of 3rd version and i wanted this post to be that notice.
We still working on the 3rd version (the last alpha) code name "making bitAssets usable everywhere Bitcoin is accepted".
We are integrating the wallet backend with liquidity providers like CryptoHedge (through metaexchange.info) and also in talks with other bitcoin service providers.
@cass has joined our team and is helping us with the new design and branding,
Anyway, the 3rd release will still be using our old-and-ugly design with minor modifications while @cass works on the new one for v4.
So v3 will look something like this.
(http://i.imgur.com/BVFCTCT.png)
And v4 will look something like this.
(http://i.imgur.com/xMUnUkY.jpg)
------------------------------
Were we are going.
We want to build a company on top of the wallet service.
In fact we already have a name for it ... LIME.
Pablo (@dargonar), besides working on the frontend, is working on a pitch deck to show to potential investors.
The 100% delegate position is helping us bootstrap the company, but as you may know this can't even pay one developer salary. So we are looking to raise seed funding.
We believe that LIME besides being for profit will also bring value to the BitShares shareholders as a whole.
As bytemaster said "Every delegate should have a business plan", we are going in that direction.
Besides all this, we are working side-by-side with @matt608, @fran2k and @rgcrypto holding meetups in the Buenos Aires Bitcoin Center, teaching the local Bitcoin community about BitShares and bitAssets, doing paper wallets giveaways, creating a video about BitShares in spanish with the people from btcenespanol.com and (as soon as i have some time) helping BTCTrip.com to accept bitUSD as a payment method.
Thats all for now, stay tuned for v3 update.
Matias
-
+5% +5% +5%
-
LIME? http://www.lime.com/ ?
-
LIME? http://www.lime.com/ ?
More Infos will follow...
-
Love the progress.
-
@ElMato
Talking about paper wallets I can offer assistance with creation of (preloaded) paper wallets (SVG formated) ..
Also would like to simplify cold storage that way .. can you tell me if your mobile wallet will be able to decode BIP38 encoded private keys?
-
Awesome update and that v4 looks amazing! I'm really desperate for this on Android. Keep up the great work :) Thanks.
-
@ElMato
Talking about paper wallets I can offer assistance with creation of (preloaded) paper wallets (SVG formated) ..
Also would like to simplify cold storage that way .. can you tell me if your mobile wallet will be able to decode BIP38 encoded private keys?
Hi Xeroc, thanks for your help will let @fran2k know about that.
Bip38 will be supported in the future but is not high prio right now.
If you want to help us in the implementation you can extend the cordova plugin we are using for the crypto part.
https://github.com/latincoin-com/cordova-plugin-bitwallet
-
With current price,will you stop develop the mobile wallet? :-[
-
@lzr1900, We are working 12 hours a day in this project and we are not working for the delegate payment, it just helping us paying the rent of our office.
I know that you are expecting results now, and we will release soon.
Just give us some more days.
-
@lzr1900, We are working 12 hours a day in this project and we are not working for the delegate payment, it just helping us paying the rent of our office.
I know that you are expecting results now, and we will release soon.
Just give us some more days.
+5%
-
@lzr1900, We are working 12 hours a day in this project and we are not working for the delegate payment, it just helping us paying the rent of our office.
I know that you are expecting results now, and we will release soon.
Just give us some more days.
+5%
-
@lzr1900, We are working 12 hours a day in this project and we are not working for the delegate payment, it just helping us paying the rent of our office.
I know that you are expecting results now, and we will release soon.
Just give us some more days.
good to know +5%
-
@lzr1900, We are working 12 hours a day in this project and we are not working for the delegate payment, it just helping us paying the rent of our office.
I know that you are expecting results now, and we will release soon.
Just give us some more days.
good to know +5%
Why? as far as I remember you had sold all of your bts(thats what you said), did you buy them back? I'm just curious.
-
@lzr1900, We are working 12 hours a day in this project and we are not working for the delegate payment, it just helping us paying the rent of our office.
I know that you are expecting results now, and we will release soon.
Just give us some more days.
Although we all knows that development is very difficult,can you give us some rough ETA?
I think most of us is losing patience now. An ETA or updates would be good.
-
Besides all this, we are working side-by-side with @matt608, @fran2k and @rgcrypto holding meetups in the Buenos Aires Bitcoin Center, teaching the local Bitcoin community about BitShares and bitAssets, doing paper wallets giveaways, creating a video about BitShares in spanish with the people from btcenespanol.com and (as soon as i have some time) helping BTCTrip.com to accept bitUSD as a payment method.
Great news ElMato, lot of exciting things hapenning.
And here is the video done by Joaquin from elbitcoin.org ! The costs were funded 50/50 by @matt608 and @elmato delegates.
https://www.youtube.com/watch?v=JyBMl9Hx8YY
-
top work!
https://www.youtube.com/watch?v=JyBMl9Hx8YY
-
Besides all this, we are working side-by-side with @matt608, @fran2k and @rgcrypto holding meetups in the Buenos Aires Bitcoin Center, teaching the local Bitcoin community about BitShares and bitAssets, doing paper wallets giveaways, creating a video about BitShares in spanish with the people from btcenespanol.com and (as soon as i have some time) helping BTCTrip.com to accept bitUSD as a payment method.
Great news ElMato, lot of exciting things hapenning.
And here is the video done by Joaquin from elbitcoin.org ! The costs were funded 50/50 by @matt608 and @elmato delegates.
https://www.youtube.com/watch?v=JyBMl9Hx8YY
i never see nothing writed on elbitcoin.org about bitshares
the video is very limited just explain the peg for 500$
-
nobody care their progress???
I do ..
-
I also care.
Allow me to introduce myself. My name is Etienne, 38 years old, father of 2. I'm a programmer-designer and have been involved as of lately with the Bitcoin Association at Buenos Aires.
I participated in several talks at their meetups, and together with fran2k & ElMato from this forum, and many other collaborators, we are constantly pushing forward BitShares here in Buenos Aires.
I can personally atest to the ongoing non-stop coding by ElMato, so please be patient. He is on it 100%.
I can also atest to all the energy being put to gather more and more people to our bitshares meetups, to giving bitUSD's away to attendees while instructing them on platforms, wallets and other important data surrounding the bitshares phenomenon.
We are building a community and we are loving it!
-
I also care.
Allow me to introduce myself. My name is Etienne, 38 years old, father of 2. I'm a programmer-designer and have been involved as of lately with the Bitcoin Association at Buenos Aires.
I participated in several talks at their meetups, and together with fran2k & ElMato from this forum, and many other collaborators, we are constantly pushing forward BitShares here in Buenos Aires.
I can personally atest to the ongoing non-stop coding by ElMato, so please be patient. He is on it 100%.
I can also atest to all the energy being put to gather more and more people to our bitshares meetups, to giving bitUSD's away to attendees while instructing them on platforms, wallets and other important data surrounding the bitshares phenomenon.
We are building a community and we are loving it!
Hi very glad to hear that ? thank you ,
-
I also care.
Allow me to introduce myself. My name is Etienne, 38 years old, father of 2. I'm a programmer-designer and have been involved as of lately with the Bitcoin Association at Buenos Aires.
I participated in several talks at their meetups, and together with fran2k & ElMato from this forum, and many other collaborators, we are constantly pushing forward BitShares here in Buenos Aires.
I can personally atest to the ongoing non-stop coding by ElMato, so please be patient. He is on it 100%.
I can also atest to all the energy being put to gather more and more people to our bitshares meetups, to giving bitUSD's away to attendees while instructing them on platforms, wallets and other important data surrounding the bitshares phenomenon.
We are building a community and we are loving it!
BitShares embassy No.1 :) +5%
-
I also care.
Allow me to introduce myself. My name is Etienne, 38 years old, father of 2. I'm a programmer-designer and have been involved as of lately with the Bitcoin Association at Buenos Aires.
I participated in several talks at their meetups, and together with fran2k & ElMato from this forum, and many other collaborators, we are constantly pushing forward BitShares here in Buenos Aires.
I can personally atest to the ongoing non-stop coding by ElMato, so please be patient. He is on it 100%.
I can also atest to all the energy being put to gather more and more people to our bitshares meetups, to giving bitUSD's away to attendees while instructing them on platforms, wallets and other important data surrounding the bitshares phenomenon.
We are building a community and we are loving it!
BitShares embassy No.1 :) +5%
Do the guys in Buenos Aires have a meetup.com page?
By adding "BitShares" to the meetup page's list of topics under "Group Settings", it will show up on http://bitshares.meetup.com
-
I view the project, It seems code with cordova(js and html5), what's difference mobile wallet between light wallet such as wallet.bitshares.org?
does the mobile wallet need down the blockchain? thanks.
-
I also care.
Allow me to introduce myself. My name is Etienne, 38 years old, father of 2. I'm a programmer-designer and have been involved as of lately with the Bitcoin Association at Buenos Aires.
I participated in several talks at their meetups, and together with fran2k & ElMato from this forum, and many other collaborators, we are constantly pushing forward BitShares here in Buenos Aires.
I can personally atest to the ongoing non-stop coding by ElMato, so please be patient. He is on it 100%.
I can also atest to all the energy being put to gather more and more people to our bitshares meetups, to giving bitUSD's away to attendees while instructing them on platforms, wallets and other important data surrounding the bitshares phenomenon.
We are building a community and we are loving it!
I'm glad to see you here finally!
Do the guys in Buenos Aires have a meetup.com page?
By adding "BitShares" to the meetup page's list of topics under "Group Settings", it will show up on http://bitshares.meetup.com
Not yet. I tried to create it some weeks ago but it asked for a CC. I'm waiting for someone on the team to register it.
We were using the Bitcoin one, in which I'm also organizer. http://www.meetup.com/Bitcoin-Argentina/
-
Do the guys in Buenos Aires have a meetup.com page?
By adding "BitShares" to the meetup page's list of topics under "Group Settings", it will show up on http://bitshares.meetup.com
Not yet. I tried to create it some weeks ago but it asked for a CC. I'm waiting for someone on the team to register it.
We were using the Bitcoin one, in which I'm also organizer. http://www.meetup.com/Bitcoin-Argentina/
can help setting meetup page up! PLs don't hesitate to ping me ... or just let me know who i should add as admin/owner then .... thx
-
I also care.
Allow me to introduce myself. My name is Etienne, 38 years old, father of 2. I'm a programmer-designer and have been involved as of lately with the Bitcoin Association at Buenos Aires.
I participated in several talks at their meetups, and together with fran2k & ElMato from this forum, and many other collaborators, we are constantly pushing forward BitShares here in Buenos Aires.
I can personally atest to the ongoing non-stop coding by ElMato, so please be patient. He is on it 100%.
I can also atest to all the energy being put to gather more and more people to our bitshares meetups, to giving bitUSD's away to attendees while instructing them on platforms, wallets and other important data surrounding the bitshares phenomenon.
We are building a community and we are loving it!
+5% Welcome Etienne :)
-
Do the guys in Buenos Aires have a meetup.com page?
By adding "BitShares" to the meetup page's list of topics under "Group Settings", it will show up on http://bitshares.meetup.com
Not yet. I tried to create it some weeks ago but it asked for a CC. I'm waiting for someone on the team to register it.
We were using the Bitcoin one, in which I'm also organizer. http://www.meetup.com/Bitcoin-Argentina/
Just created with Robrigo's help: http://www.meetup.com/BitShares-Buenos-Aires/
I'm wondering what's better BitShares Buenos Aires or BitShares Argentina? What do you guys think?
Website (bitshares.com.ar already registered) and FB page will be next.
-
It is indeed kind of frustrating to so no updates at all :(
-
This mobile wallet avaiable yet?
I want tried, I hope if available , its ease of use and security remains the primary
-
dead
-
dead
i want more updates, but your posts are not helping!
The last update said they used it in their meetup
1. why is the github not updated since January?
2. to get something "official" from the team would be good, you are a elected delegate and your "employer" has the need to get informed sometimes.
-
dead
i want more updates, but your posts are not helping!
The last update said they used it in their meetup
1. why is the github not updated since January?
2. to get something "official" from the team would be good, you are a elected delegate and your "employer" has the need to get informed sometimes.
https://github.com/latincoin-com/bitwallet/commits/dargon-dev-btc
Almost... Beta?
-
Hi everyone, sorry for the lack of updates in the last weeks, Pablo and I have been busy with personal issues, I being a father again with some minors issues and Pablo moving from his house.
I will focus this week to get a release ASAP for you to test.
@Shentist:
1) You have to look not in the master branch but the dev ones.
Also there is a lot of work in the backend that is not being published in github but in our private repo.
2) True
@xeroc: I know it is frustating, we will try to update more often.
@lzr1900: Thanks for your support, but we are not dead.
-
Hi everyone, sorry for the lack of updates in the last weeks, Pablo and I have
been busy with personal issues, I being a father again with some minors issues
and Pablo moving from his house.
Congratulations!!!!
My take on that: Family comes first! Enjoy the time with your kids!
-
Hi everyone, sorry for the lack of updates in the last weeks, Pablo and I have been busy with personal issues, I being a father again with some minors issues and Pablo moving from his house.
I will focus this week to get a release ASAP for you to test.
Ey! Congrats! alpha2 still running flawlessly on my phone ;)
-
any news with android wallet ?
-
Hi everyone, sorry for the lack of updates in the last weeks, Pablo and I have been busy with personal issues, I being a father again with some minors issues and Pablo moving from his house.
I will focus this week to get a release ASAP for you to test.
@Shentist:
1) You have to look not in the master branch but the dev ones.
Also there is a lot of work in the backend that is not being published in github but in our private repo.
2) True
@xeroc: I know it is frustating, we will try to update more often.
@lzr1900: Thanks for your support, but we are not dead.
Congratulations!!!!
he/she have a father is working on a grandness thing ,it would change the world maybe :)
-
Just to keep everyone posted.
We are re-factoring some messy parts of the transaction list processing since it got too clumsy and is preventing us from going faster.
--- long
We are merging information that is in the blockchain (operations inside txs) with information that is private to each client (deposits, withdraws, payments), this merging is being done in the client.
Since what you will be having in the wallet is the real bitAsset (bitUSD/bitCNY,etc) no and IOU (UIA) from us, each transaction that our client send is composed of 4 operations.
1 Withdraw - in bitAsset (from client)
1 Deposit - in bitAsset (to destination)
1 Deposit - in bitAsset (to our hot wallet - service fee)
1 Withdraw - in BTS (from our hot wallet - network fee)
We know that with the new UIA features we could have setup and IOU from us that is instant redeemable for the bitAsset (using the market) and just set a transaction fee. But we think is better to just use the real bitAsset. (And the new UIA features were not available at the time we started)
Also part of this re-factoring includes the memo creation/decryption.
Is short, we are re-factoring the code that reduces each of this operations combined with the private information and generate a nice and simple row that says things like.
"10 Received from PEPE (message from pepe)" or
"300 USD deposit"
"15 USD Sent to JUAN (memo) (fee)"
"1.2 BTC sent (memo)"
"150 USD withdraw (btc address)"
-
+5%
-
+5%
-
Just to keep everyone posted.
We are re-factoring some messy parts of the transaction list processing since it got too clumsy and is preventing us from going faster.
--- long
We are merging information that is in the blockchain (operations inside txs) with information that is private to each client (deposits, withdraws, payments), this merging is being done in the client.
Since what you will be having in the wallet is the real bitAsset (bitUSD/bitCNY,etc) no and IOU (UIA) from us, each transaction that our client send is composed of 4 operations.
1 Withdraw - in bitAsset (from client)
1 Deposit - in bitAsset (to destination)
1 Deposit - in bitAsset (to our hot wallet - service fee)
1 Withdraw - in BTS (from our hot wallet - network fee)
We know that with the new UIA features we could have setup and IOU from us that is instant redeemable for the bitAsset (using the market) and just set a transaction fee. But we think is better to just use the real bitAsset. (And the new UIA features were not available at the time we started)
Also part of this re-factoring includes the memo creation/decryption.
Is short, we are re-factoring the code that reduces each of this operations combined with the private information and generate a nice and simple row that says things like.
"10 Received from PEPE (message from pepe)" or
"300 USD deposit"
"15 USD Sent to JUAN (memo) (fee)"
"1.2 BTC sent (memo)"
"150 USD withdraw (btc address)"
much clean than before, hope try it soon! +5%
-
+5% awesome just installed on note3 great job
-
api server will be unreliable until notice
-
start at 2014.12.01..
now is 2015.05.14..
still in alpha test..
good job.
-
LIME? http://www.lime.com/ ?
More Infos will follow...
More Infos will not follow.
hot air.
-
LIME? http://www.lime.com/ ?
More Infos will follow...
More Infos will not follow.
hot air.
So what's your end game here? This effort came out of nowhere and continues to progress. I am not understanding your anger. Does it conflict with, or hinder, what you're working on to add value to the ecosystem? Can you share with us what value you are bringing to the table?
Sent from my Timex Sinclair
-
LIME? http://www.lime.com/ ?
More Infos will follow...
More Infos will not follow.
hot air.
So what's your end game here? This effort came out of nowhere and continues to progress. I am not understanding your anger. Does it conflict with, or hinder, what you're working on to add value to the ecosystem? Can you share with us what value you are bringing to the table?
Sent from my Timex Sinclair
+5%
-
LIME? http://www.lime.com/ ?
More Infos will follow...
More Infos will not follow.
hot air.
So what's your end game here? This effort came out of nowhere and continues to progress. I am not understanding your anger. Does it conflict with, or hinder, what you're working on to add value to the ecosystem? Can you share with us what value you are bringing to the table?
Sent from my Timex Sinclair
I believe this project kind of represents a lot of what has happened to bts over the last year. Many promises were made and a lot of hype surrounded those promises, yet we have not seen much as far as deliverables... This is going to upset people, and they have the right to be upset as they are share holders. Some of the posts could be more positive, but I think the language barrier may be the biggest contributer to the posts coming off very harsh.
-
LIME? http://www.lime.com/ (http://www.lime.com/) ?
More Infos will follow...
More Infos will not follow.
hot air.
So what's your end game here? This effort came out of nowhere and continues to progress. I am not understanding your anger. Does it conflict with, or hinder, what you're working on to add value to the ecosystem? Can you share with us what value you are bringing to the table?
Sent from my Timex Sinclair
I believe this project kind of represents a lot of what has happened to bts over the last year. Many promises were made and a lot of hype surrounded those promises, yet we have not seen much as far as deliverables... This is going to upset people, and they have the right to be upset as they are share holders. Some of the posts could be more positive, but I think the language barrier may be the biggest contributer to the posts coming off very harsh.
Yes, I suspect frustration is a lot of it.
-
Here is an update to show where what we are doing.
Basically we have a stable backend api (v2), a stable wallet structure and a working exchange, so now all the efforts will be going into the UI.
(http://imgur.com/MXXHpSo.png)
(http://imgur.com/7ilpqMc.png)
(http://imgur.com/qqDdn3j.png)
-
wow ...
-
+5% +5% +5%
-
look closer fellas. its made for bitcoin not bts?
-
look closer fellas. its made for bitcoin not bts?
;) nope !
Outstanding dudes... congratz to limewallet team
-
Please publish the APK @ f-droid.org. There are few cryptocoin apps there (and some of us don't use the play store ;)), this will bring some more users in.
Also - haven't read the 11 pages of this thread - does this wallet support TITAN?
If not, why?
If not, any plans to implement it?
If yes, any ETA?
-
Here is an update to show where what we are doing.
Basically we have a stable backend api (v2), a stable wallet structure and a working exchange, so now all the efforts will be going into the UI.
(http://imgur.com/MXXHpSo.png)
(http://imgur.com/7ilpqMc.png)
(http://imgur.com/qqDdn3j.png)
awesome
-
Please publish the APK @ f-droid.org. There are few cryptocoin apps there (and some of us don't use the play store ;)), this will bring some more users in.
Also - haven't read the 11 pages of this thread - does this wallet support TITAN?
If not, why?
If not, any plans to implement it?
If yes, any ETA?
As I know it is different to support TITAN
-
Please publish the APK @ f-droid.org. There are few cryptocoin apps there (and some of us don't use the play store ;)), this will bring some more users in.
Also - haven't read the 11 pages of this thread - does this wallet support TITAN?
If not, why?
If not, any plans to implement it?
If yes, any ETA?
As I know it is different to support TITAN
s/different/difficult/
what BTSdac wants to say that you cannot simply support TITAN without having the need to scan every single transactions ..
I suppose the wallet will not be TITAN compatible in terms of receiving via TITAN .. but I guess you will be able to send funds to a registered account via TITAN
-
Sorry xeroc, what exactly is the problem in scanning all transactions? Not sure if I follow.
Sure it would be slower and it would eat up more battery. Perhaps default to non-TITAN on mobile, have a way to enable it with a loud disclaimer about reduced battery life and what not.
Coupled with supporting >1 wallet (not sure if it already does) this should make it pretty practical.
I for one would not use the software without TITAN .. but I guess I'm in the minority :)
And what about f-droid ? Any plans to make the app available there?
-
Sorry xeroc, what exactly is the problem in scanning all transactions? Not sure if I follow.
Sure it would be slower and it would eat up more battery. Perhaps default to non-TITAN on mobile, have a way to enable it with a loud disclaimer about reduced battery life and what not.
You also need to know the WHOLE blockchain .. and that does not fit well with "leightweight" mobile wallet :)
Coupled with supporting >1 wallet (not sure if it already does) this should make it pretty practical.
I for one would not use the software without TITAN .. but I guess I'm in the minority :)
not supporting TITAN does not mean you cannot use registered account names .. though you can only receive publicly .. not anonymously ..
-
You also need to know the WHOLE blockchain .. and that does not fit well with "leightweight" mobile wallet :)
Right, good point. Do we have some sort of SPV ?
not supporting TITAN does not mean you cannot use registered account names .. though you can only receive publicly .. not anonymously ..
I am aware. My issue is with receiving publicly, you could say I'm someone who enjoys the right to privacy (have you heard anyone else bitching about how difficult it can be sometimes to access the forum over tor? :)).
-
I am aware. My issue is with receiving publicly, you could say I'm someone who enjoys the right to privacy (have you heard anyone else bitching about how difficult it can be sometimes to access the forum over tor? :)).
counter question: How easy is it for you to register a new mail account with a random name?
with the difference that in bitshares you can register in a decentralized manner .. no need to send your "IP" to googlemail or hotmail ..
However, I am not sure if the BitShares client is TOR compatible already .. but I'd say 'wallet.bitshares.org' is ..
-
The client isn't tor compatible. Which reminds me, ORBOT support for the android app would be pretty neat.. moot point of the phone is rooted, but I suppose most users don't have rooted phones.
And sure, but it only takes one slippage for anyone to be able to link your entire balance to your public account name.
At least with bitcoin and others you can just generate a new address. And even there using Tor is preferable so that linking transactions by IP is not possible.
With bitshares you're one command away from revealing the balance of any non-titan registered account, as you know!
Essentially, a privacy nightmare.
-
Please publish the APK @ f-droid.org. There are few cryptocoin apps there (and some of us don't use the play store ;)), this will bring some more users in.
Also - haven't read the 11 pages of this thread - does this wallet support TITAN?
If not, why?
If not, any plans to implement it?
If yes, any ETA?
@Karnal, @xeroc is right on what he is saying.
TITAN support wont be available in the first release but we are committed to support it as soon as the infrastructure in the network is ready.
I really don't know the current status of the mail subsystem (that will let you notify a user which transaction to look in the blockchain)
We can easily support outgoing TITAN transactions to "titan accounts" but the real value is to support incoming TITAN transactions.
-
Sounds good, and in case it wasn't clear from my previous posts, the effort is appreciated. It's much better to have a mobile wallet without TITAN for now than having no mobile wallet at all.
So keep up the good work!
Any word on publishing the apk to f-droid ? I could test the app if it lands there too and begin spreading the gospel around here as well.
-
Any word on publishing the apk to f-droid ? I could test the app if it lands there too and begin spreading the gospel around here as well.
Sure, we will also publish to f-droid.
-
Looking forward to that, keep me posted!
-
Nice update, keep up the hard work guys!
-
since your latest update was 2.5 months ago,any update?
-
LIME? http://www.lime.com/ ?
More Infos will follow...
hello cass .is this site relate to limewallet?
-
What's the plan with this? Will there be a mobile wallet ready for when 2.0 comes out ?
I assume the previous (0.x) wallet has been more or less abandoned. What's the status?
Thanks.
-
LIME? http://www.lime.com/ ?
More Infos will follow...
hello cass .is this site relate to limewallet?
no @Krills ..
@ElMato : could pls give a small status update of limewallet!?
thx in advance
-
The wallet is already working with 0.9.X.
We will release the beta here this week for the comunity to test. On the other side we are already porting our backend to cope with the BTS 2.0.
-
The wallet is already working with 0.9.X.
We will release the beta here this week for the comunity to test. On the other side we are already porting our backend to cope with the BTS 2.0.
awesome +5% +5%
-
The wallet is already working with 0.9.X.
We will release the beta here this week for the comunity to test. On the other side we are already porting our backend to cope with the BTS 2.0.
I hope this will be true,real true.
-
ANN LimeWallet Beta
https://bitsharestalk.org/index.php/topic,17900.0.html (https://bitsharestalk.org/index.php/topic,17900.0.html)
-
ANN LimeWallet Beta
https://bitsharestalk.org/index.php/topic,17900.0.html (https://bitsharestalk.org/index.php/topic,17900.0.html)
+5%
-
how to update to bts2.0 mobile wallet?
can't output privatekey I send some bts into account created by this wallet before
-
how to update to bts2.0 mobile wallet?
can't output privatekey I send some bts into account created by this wallet before
Here is the latest update from ElMato:
https://bitsharestalk.org/index.php/topic,20634.msg266668.html#msg266668