Show Posts
|
Pages: [1] 2 3 4 5 »
|
We can develop for you in python (or in Java, C++ and others). For a quick sample check out the wallet info tool (forked from brilliant pywalletinfo, but with almost all known coins support and many other improvements) https://github.com/unicoinex/walletinfo
|
|
|
How much are you willing you pay to the shipper? Besides the cost of item+shipment.
|
|
|
You might get a response for free if you post your queries here.
|
|
|
Man you are really good for business marketing! I almost started to get a feeling you two are affiliated! Is there anything we can do for you?
|
|
|
We are still looking. So if you come upon this thread, we are still looking to hire someone. (Unless I finish the dev myself.)
Sent you a PM.
|
|
|
We're getting ready to release the next build with MintPal support in a day or two. Feel free to request other exchanges here!
|
|
|
Do you need litecoin+bitcoin or only litecoin?
|
|
|
How's everyone liking this app? Just from Google play store it has 5 stars, 100+ downloads, and 11 reviews. Unicoinex is doing a good job on keep it updated and free from bugs, I'd like to see more reviews and downloads though since I helped test it Bump for COINTRA! We are seeing gradual adoption and are giving it its due time to get noticed. So far feedback has been great and those who are using it can't trade without it!
|
|
|
Our app Cointra has been said to offer bitcoinwisdom like charts so I believe we can offer such for your site. Link to app in my signature
|
|
|
BTC 1.0015 well received. Thank you! Will check and update on the new additions and errors. Edit: Found the bug with Ultracoin/Blackcoin etc. they use a slightly different format, nothing big and should be working in the next push tomorrow. Ultracoin was missing from the coins list, added it, blackcoin seems to be working fine. Edit 2: The VTC error is related to the vertcoin explorer. Try pasting the address at the end of: https://explorer.vertcoin.org/chain/Vertcoin/q/addressbalance/ and you would see the same behavior. I will try to find another explorer if I can, or we have to live with this bug.
|
|
|
Removed db_env creation, no more __db files and the app is now fully readonly and should work any filesystem, tried on read-only filesystem and worked without errors.
|
|
|
Fixed the passphrase segfault. Make sure you install pycryto python module or else decryption will be dead slow. Everything should work as expected now.
Great. I might not have time to test for a while, so please send me your BTC address and I'll send 0.75 BTC now and the rest after I test. In the one test I did I got an error message: $ python wi.py --is-encrypted --wallet=/home/user/wallet1.dat Traceback (most recent call last): File "wi.py", line 1823, in <module> db_env = create_env(db_dir) File "wi.py", line 1158, in create_env (DB_CREATE | DB_INIT_LOCK | DB_INIT_LOG | DB_INIT_MPOOL | DB_INIT_TXN | DB_THREAD | DB_RECOVER)) bsddb.db.DBInvalidArgError: (22, 'Invalid argument -- mmap: Invalid argument')
Tried it with a couple wallet files and got the same error. The user has read/write permission to the directory. I have the python-crypto package installed. Could it be the bsddb module version you have? I tried the exact same command and got no error. I will just post a set up guide to make sure we're installing the correct python/module versions. Actually just did a quick search, it could be python version issue as mentioned http://stackoverflow.com/questions/15958917/bsddb-4-2-52-dbinvalidargerror-22-invalid-argumentCan you try with python 2.7? If not I will downgrade to python 2.5 Actually, I figured out what is causing the problem. I'm using VirtualBox and the wallet files are on a shared drive, and for some reason BSDDB can't work with that directory. All other tools I've used can read/write fine to it, they treat it just like any other directory. My suggested fix will actually fix two issues: - Suggested fix: Create a temporary working directory in /tmp, do the operation, remove the directory. This addresses the issue with the shared drive and also fixes the issue that currently lots of __db.00X files are left behind in the directory after the script finishes. If you can do the operation using the temporary directory and leaving the wallet file in its current place, that is best. If you need to have the wallet file in the temporary directory, then copying it over would be ok. And please send me your Bitcoin address so I can send you half now. I've been slow to test but I want to make sure you know I'm good for the BTC and to keep you motivated to make these fixes. /tmp is a good idea and I will implement that. I am completely fine with receiving the whole amount once you're happy with the script, however if you really want to send half now then you can use the address on my profile i.e. 16xe1bCgnDLe27FAWHb4pmKzjiEWzMxLG8 Thanks
|
|
|
Fixed the passphrase segfault. Make sure you install pycryto python module or else decryption will be dead slow. Everything should work as expected now.
Great. I might not have time to test for a while, so please send me your BTC address and I'll send 0.75 BTC now and the rest after I test. In the one test I did I got an error message: $ python wi.py --is-encrypted --wallet=/home/user/wallet1.dat Traceback (most recent call last): File "wi.py", line 1823, in <module> db_env = create_env(db_dir) File "wi.py", line 1158, in create_env (DB_CREATE | DB_INIT_LOCK | DB_INIT_LOG | DB_INIT_MPOOL | DB_INIT_TXN | DB_THREAD | DB_RECOVER)) bsddb.db.DBInvalidArgError: (22, 'Invalid argument -- mmap: Invalid argument')
Tried it with a couple wallet files and got the same error. The user has read/write permission to the directory. I have the python-crypto package installed. Could it be the bsddb module version you have? I tried the exact same command and got no error. I will just post a set up guide to make sure we're installing the correct python/module versions. Actually just did a quick search, it could be python version issue as mentioned http://stackoverflow.com/questions/15958917/bsddb-4-2-52-dbinvalidargerror-22-invalid-argumentCan you try with python 2.7? If not I will downgrade to python 2.5
|
|
|
Still getting the same error it looks like Wallet could be damaged beyond repair
|
|
|
You mentioned in PM that its not bitcoin wallet, pywallet works with bitcoin, namecoin or litecoin out of the box (or others as long as you enter otherversion and they use the private key = otherversion + 128).
Can you tell which altcoin wallet is it?
The wallet is for shibecoin try running: ./pywallet --datadir=/home/diesel/Desktop --otherversion=63 --dumpwalletDo I need to have the shibecoin wallet installed on the machine that I got pywallet on? or is wallet.dat all I need because as of right now I have a virtual machine running on my windows 7 with ubuntu on it with pywallet.py & wallet.dat on the virtual machine Desktop I will try the above line very shortly You only need wallet.dat file
|
|
|
You mentioned in PM that its not bitcoin wallet, pywallet works with bitcoin, namecoin or litecoin out of the box (or others as long as you enter otherversion and they use the private key = otherversion + 128).
Can you tell which altcoin wallet is it?
The wallet is for shibecoin try running: ./pywallet --datadir=/home/diesel/Desktop --otherversion=63 --dumpwallet
|
|
|
Fixed the passphrase segfault. Make sure you install pycryto python module or else decryption will be dead slow. Everything should work as expected now.
|
|
|
You mentioned in PM that its not bitcoin wallet, pywallet works with bitcoin, namecoin or litecoin out of the box (or others as long as you enter otherversion and they use the private key = otherversion + 128).
Can you tell which altcoin wallet is it?
|
|
|
Committed with all the fixes. Passphrase decryption is not working and gives segmentation fault, found the problem statement will be fixing it soon. In the meantime if you can check if all your previously mentioned issues have been resolved. Also note I have put a different blockchain explorer for zetacoin so balance should work now.
|
|
|
|