Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - ElMato

Pages: 1 ... 9 10 11 12 13 14 15 [16] 17 18 19 20
General Discussion / Re: Mobile Wallet - Testers needed
« on: December 04, 2014, 05:54:47 pm »
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?

General Discussion / Re: Mobile Wallet - Testers needed
« on: December 03, 2014, 01:16:27 am »
@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.

General Discussion / Re: Mobile Wallet - Testers needed
« on: December 02, 2014, 01:29:05 pm »
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


We are very pleased for the reception of the wallet and this encourage us to work even harder.

This is how our vision goes regarding bitUSD in Argentina.

Today Bitcoin in Argentina is being used for:
- Speculation.
- Bring money/Receive payments from overseas (at higher rates than the official dollar rate)
- Merchants to avoid credit card fees and to get the money in banks earlier. (and some of them to avoid taxes)

To a minor extent:
- Tourists exchanging Bitcoin for ARS with OTC brokers.

Bitcoin is not used as a currency but as a way of transmitting money.

The problem with the dollar in Argentina is not one of a supply for small amounts. (Importers are the ones who are restricted).
If you want to buy 1000 USD you can do it on every corner of Buenos Aires or any other major city.

Common people keep part of their income in USD, but when they need to use it they can't without exchange them back to ARS.
Its a problem of convenience, you don't go every day to your USD dealer looking for ARS.
Besides that everyone here know the exchange rate of USD, the economy is not dollarized (Argentina is not Ecuador).

Thats why a bitUSD wallet that allows consumers to spend their USD in everyday purchases has great potential.
Besides that this currency connect the users to a global market, allows them to send instant remittances and gives a bank account to non bankarized ones.


Our short term goals are:
 - Evangelize the Argentina Bitcoin community.
 - Use the existing Bitcoin infrastructure to convert ARS<=>bitUSD.

We are willing to work together in a complementary manner with matt608 and MethodX in the strategy of bitUSD for Argentina.

Going back to work!

General Discussion / Re: Mobile Wallet - Testers needed
« on: December 01, 2014, 09:40:56 pm »
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)


"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.

General Discussion / Re: Mobile Wallet - Testers needed
« on: December 01, 2014, 10:37:06 am »
Maybe a wallet_rescan_blockchain from one block before the transaction's block?

General Discussion / Re: Mobile Wallet - Testers needed
« on: December 01, 2014, 10:29:12 am »
And I suppose it only works for non-TITAN addresses?
Yep ..

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)

General Discussion / Re: Mobile Wallet - Testers needed
« on: December 01, 2014, 10:17:53 am »
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" )
    - 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.

General Discussion / Re: Mobile Wallet - Testers needed
« on: December 01, 2014, 10:03:20 am »
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.

General Discussion / Re: Mobile Wallet - Testers needed
« on: December 01, 2014, 10:01:17 am »
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

@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!

General Discussion / Re: Mobile Wallet - Testers needed
« on: December 01, 2014, 09:11:44 am »
Awesome .. +5%


BTW, "BTSX" should be "BTS" .. also in the addresses and pubkeys

Is version 0.4.24 already working with the BTS prefix?

- 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 ...

General Discussion / Mobile Wallet - Testers needed
« on: December 01, 2014, 08:57:20 am »


* 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.


1) Export your wallet
2) Install alpha2
3) Restore wallet


Bitwallet-debug.apk shasum f71c67062343232b3ddf4e6bdf6d08c64801b836


* 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

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

Screenshots and apk

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 (
- 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.

Code: [Select]
 "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

This api lets you know the balance and transaction history of an address.

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.

sub BTSX9pTBfYkFwmUm46XTaeTLukGDrupobHwzc
sub xpub661MyMwAqRbcEYS8w7XLSVeEsBXy79zSzH1J8vCdxAZningWLdN3zgtU6T6MHAZTgj9H6QNfLWByR1Dj4exUQ8FqYv9s7KecprYm7unUkX1:5

General Discussion / Re: 2014 Proof of Honor (POH) Awards - Nominations
« on: November 24, 2014, 12:29:17 am »

General Discussion / Re: Invite only community marketing forum.
« on: November 22, 2014, 06:59:51 am »
Just signed up, please approve!

I was using the cli client but wanted to take a screenshot so i closed the cli and started the GUI version.

I went to the console first (inside the GUI) and type "wallet_open test" (because i wanted to see if a missing transaction was finally there)

The GUI locks, i try to put the "test" wallet password, it didn't work so i re-entered the "default" wallet password .. i'm in again.

No connection ... and after a while (1 minute) it starts to download the blockchain from the beginin. (Your last block is 10xd old message)

Code: [Select]
(wallet closed) >>> info
  "blockchain_head_block_num": 23970,
  "blockchain_head_block_age": "15 weeks old",
  "blockchain_head_block_timestamp": "2014-07-22T01:27:30",
  "blockchain_average_delegate_participation": "0.01 %",
  "blockchain_confirmation_requirement": 1,
  "blockchain_delegate_pay_rate": "2.31959 BTSX",
  "blockchain_share_supply": "1,999,998,736.91903 BTSX",
  "blockchain_blocks_left_in_round": 68,
  "blockchain_next_round_time": "at least 11 minutes in the future",
  "blockchain_next_round_timestamp": "2014-11-05T04:50:50",
  "blockchain_random_seed": "45b49063507163d58a061907f000ee8122e71d6f",
  "client_data_dir": "/Users/matias/Library/Application Support/BitShares X",
  "client_version": "v0.4.23.1",
  "network_num_connections": 0,
  "network_num_connections_max": 200,
  "network_chain_downloader_running": false,
  "network_chain_downloader_blocks_remaining": null,
  "ntp_time": "2014-11-05T04:39:30",
  "ntp_time_error": -0.051547999999999997,
  "wallet_open": false,
  "wallet_unlocked": null,
  "wallet_unlocked_until": null,
  "wallet_unlocked_until_timestamp": null,
  "wallet_last_scanned_block_timestamp": null,
  "wallet_scan_progress": null,
  "wallet_block_production_enabled": null,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null

And now i'm stuck at block 23970.

    th_a  chain_database.cpp:573 switch_to_fork, reverting         chain_database.cpp:1617
20141105T043620.676411 th_a:invoke handle_message                store ] storing error in database: {"code":6,"name":"key_not_found_exception","message":"Key Not Found","stack":[{"context":{"level":"error","file":"level_map.hpp","line":106,"method":"fetch","hostname":"","thread_name":"th_a","timestamp":"20141105T043620.676094"},"format":"unable to find key ${key}","data":{"key":"2acd1a253129d4a274efba03ca9faf8ccdbf033d"}},{"context":{"level":"warn","file":"level_map.hpp","line":116,"method":"fetch","hostname":"","thread_name":"th_a","timestamp":"20141105T043620.676114"},"format":"error fetching key ${key}","data":{"key":"2acd1a253129d4a274efba03ca9faf8ccdbf033d"}},{"context":{"level":"warn","file":"chain_database.cpp","line":1119,"method":"pop_block","hostname":"","thread_name":"th_a","timestamp":"20141105T043620.676133"},"format":"","data":{}},{"context":{"level":"warn","file":"chain_database.cpp","line":573,"method":"switch_to_fork","hostname":"","thread_name":"th_a","timestamp":"20141105T043620.676154"},"format":"","data":{"block_id":"2acd1a253129d4a274efba03ca9faf8ccdbf033d"}},{"context":{"level":"warn","file":"chain_database.cpp","line":1629,"method":"push_block","hostname":"","thread_name":"th_a","timestamp":"20141105T043620.676218"},"format":"","data":{"block_data":{"previous":"3463f500b1993d7e8b6e5b4c64db7c51f8f4c4d0","block_num":23973,"timestamp":"20140722T012800","transaction_digest":"c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0","next_secret_hash":"3aa9cac06eb3838f92baa9b235d941fef73b2038","previous_secret":"73ef8c051808fa2259579d900973aa103d43a66f","delegate_signature":"20c01cc938ba535b6e5d758ebc02a13cd4b78b936c0d846bfd9384840fb61aa30afa096847f194c9223031eb7e45b58100fb1ab9db58cb0ecf32c39b61d72ccdd1","user_transactions":[]}}},{"context":{"level":"warn","file":"client.cpp","line":1222,"method":"on_new_block","hostname":"","thread_name":"th_a","timestamp":"20141105T043620.676282"},"format":"Error pushing block ${block_number} - ${block_id}","data":{"block_id":"cd1f95dca148ce7c93f4ec1c137d84085ba64f1e","block_number":23973,"block":{"previous":"3463f500b1993d7e8b6e5b4c64db7c51f8f4c4d0","block_num":23973,"timestamp":"20140722T012800","transaction_digest":"c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0","next_secret_hash":"3aa9cac06eb3838f92baa9b235d941fef73b2038","previous_secret":"73ef8c051808fa2259579d900973aa103d43a66f","delegate_signature":"20c01cc938ba535b6e5d758ebc02a13cd4b78b936c0d846bfd9384840fb61aa30afa096847f194c9223031eb7e45b58100fb1ab9db58cb0ecf32c39b61d72ccdd1","user_transactions":[]}}}]}         client.cpp:518
20141105T043620.677877 th_a:invoke handle_message           push_block ] attempt to switch to fork failed: 6 key_not_found_exception: Key Not Found
unable to find key 2acd1a253129d4a274efba03ca9faf8ccdbf033d
    th_a  level_map.hpp:106 fetch
error fetching key 2acd1a253129d4a274efba03ca9faf8ccdbf033d
    th_a  level_map.hpp:116 fetch

    th_a  chain_database.cpp:1119 pop_block

Pages: 1 ... 9 10 11 12 13 14 15 [16] 17 18 19 20