Well it was trivial, yours for free

http://www.unicoinex.com/wp-content/uploads/2014/05/index.html

Got your PM and its already in the works! Please do give me the requested details in PM

Here is an example of an API key for a BTC-e account

Key: 821FH6SF-JUFCWRJ2-JUWCHN6L-UC1CPLCP-T8UJSHNK
Secret: 55650306433dd24b1619c9f0337b297e9773e0066ee1cbe77f47042b709c6434

Feel free to ask any questions you may have and I will be glad to explain. Please allow me to explain API keys a little more here also to help other readers who aren't familiar with them.

All major exchanges allow users to generate API keys and secrets, they are separate from your username and password and you can set individual permissions for each API key. For example you can create one key pair and give it only Account Info rights, which would allow any software to only view your account information. The API keys can not be used to log in to the exchange website, instead they are to be used by specialized software to read the data you allow. API keys can be cancelled at any time, so in case you lose your phone you can cancel the API keys after logging in to your Exchange account (in Cointra we keep all API keys encrypted, with added encryption using a PIN if you enable it, so even if phone is lost it would not be trivial for someone to get your keys if you're using a pin).

I understand the need of an open source wallet since the software itself keeps your money! But in case of Cointra nothing except API Keys (not even your email) is stored by the app on the phone, everything is kept on your exchange and it uses the API keys you configure to allow you to view/trade your funds on your configured exchange. If the app corrupts, or phone is lost, all you have to do is delete/disable old API keys by logging on to your Exchange and create new API keys when needed.

It is a closed source app but since this app uses API Keys and not Logins, you fully control what level of access the app can ever have. For the mobile security, Android uses detailed permissions specification and the app requires no special permissions besides standard ones that give it access only to its own data and those permissions are shown during the install by Play store.

Regardless of open or closed source, whenever using an API based trading software, one can remove the risks by setting the right permissions on the API key. For Cointra you don't need any withdrawal, deposit, transfer rights on the API keys so make sure you don't add them. You can even start with read-only API keys making it 100% risk free to start.

That being said, we are very much open to your suggestions, and if you believe that open sourcing the app would be a critical factor for you and like minded users, we would consider open sourcing it. So far we have seen that majority of the users don't compile their own mobile apps even if they are open source (based on Play Store install counts of the open source apps, like the Bitcoin Wallet). Much different than desktop apps where majority compile from source (themselves or by their OS distribution).

Thank you for all for your interest. The app has been released. Please read the announcement https://bitcointalk.org/index.php?topic=598514.0

Videos

• How to generate BTC-e API Keys for adding to Cointra
• How to generate Bistamp API Keys for adding to Cointra

Release Notes

1.0 build 22
- News source CoinBuzz added
- Cryptsy new added pairs now instantly available

1.0 build 24
- Chinese translation
- Fix force close on some I9100 and N7x00 phones

1.0 build 25
- Russian translation

1.0 build 26
- More control over trend chart
- Search functionality
- Much improved chart/ticker load times

I bought a cheap comodo ssl cert from them, activation was fast, and after one day I had to change the host and since the old host generated and kept the private keys, I had to reissue the cert which these guys did very quickly once I requested. I would like to have access to reissue myself without requesting though.

Sorry don't have any slots for the time being. I will be releasing an open beta soon but there won't be any payment for it.

Thank you for you input on the app.

pywallet works on wallets that are updated by some Bitcoin client, the OP wants a tool that works with only the wallet.dat file and not require presence of a local blockchain. The only for that is as the OP mentions by getting balance updates from block explorers. * on second look pywallet works with block explorer. The tough part is that they want the tool to be able to work with new coins by adding coinname/blockchain url in a config file, but that would work only if all block explorers use a common api which is sadly not the case.

Starting a week ago I am receiving emails with .jar files claiming to be from different Bitcoin sites. They don't get detected as spam by any spam filter, the jar file is not detected as a virus. It seems they are sent to handpicked targets who actively work with crypto currency. The emails came from 3 different sources so far, 3 via smtp.com (already talked to them and they said they will look into it), and 2 via gmail.

I will be running the jar file in a virus testing sandbox to see what network connections it tries to make. Decompiling the jar didn't give much result since I believe it contains native binaries (for osx, windows and linux) that are run. If anyone else received and already tested these files please let me know what you found.

I have accounts at almost every exchange (including Mt.Gox, though my email was not in the gox account lists I found on the net) so it could be that my email leaked from one of those.

Anyone else experiencing these?

------------------ Headers and some content of the some emails received ------------------------

Delivered-To: XXXXXXXXXX@gmail.com
Received: by 10.182.246.1 with SMTP id xs1csp217663obc;
        Mon, 21 Apr 2014 12:12:32 -0700 (PDT)
Return-Path: <khamashtaa@gmail.com>
Received-SPF: pass (google.com: domain of khamashtaa@gmail.com designates 10.66.150.69 as permitted sender) client-ip=10.66.150.69
Authentication-Results: mr.google.com;
       spf=pass (google.com: domain of khamashtaa@gmail.com designates 10.66.150.69 as permitted sender) smtp.mail=khamashtaa@gmail.com;
       dkim=pass header.i=@gmail.com
X-Received: from mr.google.com ([10.66.150.69])
        by 10.66.150.69 with SMTP id ug5mr40109988pab.55.1398107551939 (num_hops = 1);
        Mon, 21 Apr 2014 12:12:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=snOLhcQ+SqxC85ZiOH580ss1veiwVqZSKyogNOl7fzY=;
        b=DZiC6/fAEVa4BWD/4GBPyuEjKs1pVMMGiW9YzXdyP6tkxt8icqgmYz2PxPqf+l0YOX
         +6BtdWGJQ7D3GUBKLfgFBVUCEl19R9OX4uoQMjhWthPhqfq+q/VLPgNxtHh2FPNtk6q9
         9weGvhUn5U2ioRC7dmBAFtJdvKgCU/V8TZXK+A9NRlZDg7J4OQuYFJIclfT0f0FPW+T2
         l086g3eRs5N8NCUT395o/z6QCh4j2p47VuMaM9Ld2Rn6Ib3k1jBHKct+/tQo31JD65FI
         88Z+CzDiNVjWOEyR6m81BWnXcnpVnimoEAY/HxFOOxGicSQN0QnonCsVPs66nImCOcYi
         Teeg==
MIME-Version: 1.0
X-Received: by 10.66.150.69 with SMTP id ug5mr40170349pab.55.1398107551483;
 Mon, 21 Apr 2014 12:12:31 -0700 (PDT)
Received: by 10.70.61.1 with HTTP; Mon, 21 Apr 2014 12:12:31 -0700 (PDT)
Date: Mon, 21 Apr 2014 22:12:31 +0300
Message-ID: <CAKNkiXYQTAc_r+u3x-jfJj0hZF3FQ_bLYEd5rnrt_WoiwOYurw@mail.gmail.com>
Subject: Problem in the Market
From: ahmad khamashta <khamashtaa@gmail.com>
To: undisclosed-recipients:;
Content-Type: multipart/mixed; boundary=047d7b6dc31ef77d1304f79247bb
Bcc: XXXXXXXXXX@gmail.com

--047d7b6dc31ef77d1304f79247bb
Content-Type: multipart/alternative; boundary=047d7b6dc31ef77d0f04f79247b9

--047d7b6dc31ef77d0f04f79247b9
Content-Type: text/plain; charset=UTF-8

*Hello, *

*I have Problem in my account , i try to buy all my XBT "122 Bitcoin"*
*buy when i need to process the order i got this error "attached"*

*Please i need answer or Solved for this problem ASAP*

*Thank you*

------------------------------------------------------------------------------------------------------------------------------------------------

Delivered-To: XXXXXXXXXX@gmail.com
Received: by 10.182.246.1 with SMTP id xs1csp100488obc;
        Mon, 28 Apr 2014 00:06:48 -0700 (PDT)
X-Received: by 10.68.240.99 with SMTP id vz3mr23458826pbc.93.1398668807684;
        Mon, 28 Apr 2014 00:06:47 -0700 (PDT)
Return-Path: <alewis@itbit.com>
Received: from mailer242.gate181.sl.smtp.com (mailer242.gate181.sl.smtp.com. [192.40.181.242])
        by mx.google.com with ESMTP id qf5si9774988pac.211.2014.04.28.00.06.47
        for <XXXXXXXXX@gmail.com>;
        Mon, 28 Apr 2014 00:06:47 -0700 (PDT)
Received-SPF: none (google.com: alewis@itbit.com does not designate permitted sender hosts) client-ip=192.40.181.242;
Authentication-Results: mx.google.com;
       spf=neutral (google.com: alewis@itbit.com does not designate permitted sender hosts) smtp.mail=alewis@itbit.com;
       dkim=pass header.i=@smtp.com
Return-Path: <alewis@itbit.com>
X-MSFBL: aHNhaG1lZEBnbWFpbC5jb21AMTkyXzQwXzE4MV8yNDJAU2VuZEJsYXN0ZXJfMkA=
DKIM-Signature: v=1; a=rsa-sha256; d=smtp.com; s=smtpcomcustomers; c=relaxed/simple;
   q=dns/txt; i=@smtp.com; t=1398668806;
   h=From:Subject:To:Date:MIME-Version:Content-Type;
   bh=FsfC8XmgPRDRepb53Yb8HgKVlGjtEhsMC2Zsr4pvMGo=;
   b=PYrnG1ZsdZweyzCBpvSTu9GZXCQu7pCZPrk3Izl2W/IYaUlRP8WxvAvb3vGUxdTb
   X3/AzJ966SmS5GlHG3FDOnattTzpc0jPPCf8CwWH7uGHC3Nwt5V270YnKrlcff/X
   Hs+uLvCNqR78MIhHwHb8h4XkgzfDV8G2MERKFMzmkj0=;
Received: from [216.55.179.130] ([216.55.179.130:58769] helo=216-55-179-130.dedicated.codero.net)
   by sl-mta06.smtp.com (envelope-from <alewis@itbit.com>)
   (ecelerity 3.5.5.39309 r(Platform:3.5.5.0)) with ESMTPSA (cipher=AES256-SHA)
   id 55/1B-09095-50EFD535; Mon, 28 Apr 2014 07:06:46 +0000
From: "ItBit" <alewis@itbit.com>
Message-ID: <55.1B.09095.50EFD535@sl-mta06>
Subject: ItBit Final Report
To: "XXXXXXX" <XXXXXXXXX@gmail.com>
Content-Type: multipart/mixed; boundary="Si3q2MkLplfvSjo1bPsfGhL=_Zd1lqAOnT"
MIME-Version: 1.0
Organization: ItBit
Date: Mon, 28 Apr 2014 00:06:46 -0700
X-SMTPCOM-Tracking-Number: 49f61f3c-42d5-47a7-91ca-0631251aca4c
X-SMTPCOM-Sender-ID: 6001689
X-SMTPCOM-Spam-Policy: SMTP.com is a paid relay service. We do not tolerate UCE of any kind. Please report it ASAP to abuse@smtp.com


This is a multi-part message in MIME format

--Si3q2MkLplfvSjo1bPsfGhL=_Zd1lqAOnT
Content-Type: multipart/alternative;
   boundary="E3ds9G5Tm1O3h=_2A5t6vfIbwqcOc6GQmQ"

--E3ds9G5Tm1O3h=_2A5t6vfIbwqcOc6GQmQ
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

=EF=BB=BFHello,
We are sorry to late , we attach in this email all the information you=
 need about your account with us.
if you have any qouestion please contact us again.
Thank you
Antony Lewis
Business Development
https://www.itbit.com | alewis@itbit.com | +65 9296 4222

Thank you all for the interest, I have enough testers now. Will contact those who requested via PM if I need more.

Can you tell me what are your charges to translate a software from English to Russian? Do you charge per word or per lump sum? Are revisions included (in case 1-2 words change within 1 month of translation)?

You might want to fix your typo in the subject line (Hebrew). Its not giving a good first impression

Details are provided in PM to those who want to beta-test as per the terms on the first post.

Some testers could not download, it seems like Google beta program does not work in all regions. So I am opening again for 2 more testers.

Yeah its possible to add chat back but that would require users to login to btc-e using their credentials! Not something we would encourage or support so that puts it off the list. One funny thing is that BTC-e censors the trollbox (curse words etc are removed from the trollbox by moderators) while the Cointra app shows everything so you might see messages there that aren't visible on trollbox!

Will look into the Cryptsy chatbox addition.

I am responding here instead of responding to all PMs. I have already selected the first group of beta testers, if you were not contacted please stay and I will e-mail you if any slot is available.

No the app does not need your account information. It needs API for trading but can work in read-only mode if you don't want to enter the API. I have sent the link to the first round of beta testers. I will select more based on their feedback.