... I tried to send to my Uno Core wallet and scanned the QR code. The problem is that the Core wallet sends back: "bitcoin:u<address>" and the result is that the Android wallet can't recognize the input. Since it's such a PITA to type a Uno addy using an android screen keyboard, is there any chance the Android wallet could just remove that "bitcoin:" from the front of the address (if it exists). That will give us a little time to resolve it on the Core wallet side. ... Actually that's a bug in the QT wallet, BW needs to fix that. I ran into that with jswallet, and I made jswallet use the correct "unobtanium:uxxxx" format as well. Hash is correct here. I'm guessing that's a simple line in the QT source, if I had more time I'd do a pull request myself... Yes, I know it needs to be addressed the core wallet. I've mentioned it. But it would be an immediate benefit to everyone if Hash could find their way to write a short function to just test the address string and if it begins with "bitcoin:", simply remove it from the string. I sense that could save us all weeks of manually pounding in long addresses with fat fingers. FWIW I think I fixed it in the QT wallet: https://github.com/unobtanium-official/Unobtanium/pull/21 |
|
|
|
... I tried to send to my Uno Core wallet and scanned the QR code. The problem is that the Core wallet sends back: "bitcoin:u<address>" and the result is that the Android wallet can't recognize the input. Since it's such a PITA to type a Uno addy using an android screen keyboard, is there any chance the Android wallet could just remove that "bitcoin:" from the front of the address (if it exists). That will give us a little time to resolve it on the Core wallet side. ... Actually that's a bug in the QT wallet, BW needs to fix that. I ran into that with jswallet, and I made jswallet use the correct "unobtanium:uxxxx" format as well. Hash is correct here. I'm guessing that's a simple line in the QT source, if I had more time I'd do a pull request myself... |
|
|
|
Who wants to beta test? HashEngineering via PM: |
|
|
|
FWIW, the UNO faucet I maintain has been empty since the 5th of this month. It doesn't need much to keep working, one or two coins seem to keep it active for a couple of months (it pays out a decreasing proportion of it's balance until it reaches the dust limit). However, maybe it's good that UNO is more scarce. It's up to you if you want to fill it: https://cryptap.us/uno/faucet/ |
|
|
|
Dedicated Android Wallet for UNO - Request funds for developmentSee the original request here: https://bitcointalk.org/index.php?topic=527500.msg10831261#msg10831261We now have 160 of our 125 UNO (at today's price) goal! udroidNXd1YNoL1DgNu8NktemcnexiBByMYou have all pushed this over the top! As they say, many hands make light work. I am glad to see this community going the extra mile to show our new Android app dev. what their work means. Good luck to HashEngineering on this endeavor, you have a strong reward waiting for you. I will proceed to payout as stated in the first post on this topic, namely 1/2 at app launch, then 1/2 a month after, or after any showstopper bugs are squashed (whichever comes first). By all means if you wish to continue, or didn't get a chance to donate please do. Keep in mind that devs. with skin in the game tend to stick around. Thanks everyone for your generosity! There hasn't been an update on this for a while, I believe HashEngineering has been on vacation. I do believe Hash has good intentions and will finish at some point but the schedule is far beyond the original idea of ~4 weeks. Individually, if you have sent funds to this address and would like them back, please PM me with a signed message from the address that you sent from and I will refund. I'm open to setting some sort of time limit before I return all funds, but I don't know what that should be and am open to suggestions. HashEngineering must be watching this thread, just received an update via PM: I am back from vacation and will hopefully have an app for testing ready in a week or less.
|
|
|
|
...
This is why, in the China project, we publicly pledge, and pay upon the completion of work. ... For future projects: do not pay in advance! Christ, haven't any of you ever done a drug deal before? We live, and survive, with neither regulation nor recourse. Pay AFTER you've tasted the weed. Nobody paid in advance, the funds are being held for the developer by me. Anyone who donated can receive their funds back from me. HashEngineering's terms are laid out in the original request for funds. In my opinion "publicly pledging" wasn't going to lure a good developer. |
|
|
|
Dedicated Android Wallet for UNO - Request funds for developmentSee the original request here: https://bitcointalk.org/index.php?topic=527500.msg10831261#msg10831261We now have 160 of our 125 UNO (at today's price) goal! udroidNXd1YNoL1DgNu8NktemcnexiBByMYou have all pushed this over the top! As they say, many hands make light work. I am glad to see this community going the extra mile to show our new Android app dev. what their work means. Good luck to HashEngineering on this endeavor, you have a strong reward waiting for you. I will proceed to payout as stated in the first post on this topic, namely 1/2 at app launch, then 1/2 a month after, or after any showstopper bugs are squashed (whichever comes first). By all means if you wish to continue, or didn't get a chance to donate please do. Keep in mind that devs. with skin in the game tend to stick around. Thanks everyone for your generosity! There hasn't been an update on this for a while, I believe HashEngineering has been on vacation. I do believe Hash has good intentions and will finish at some point but the schedule is far beyond the original idea of ~4 weeks. Individually, if you have sent funds to this address and would like them back, please PM me with a signed message from the address that you sent from and I will refund. I'm open to setting some sort of time limit before I return all funds, but I don't know what that should be and am open to suggestions. |
|
|
|
|
Just watching chartbuddy, I noted that Coinbase bids are almost always highest but seem to track the others. It seems like this for a long while. Could this be interpreted as some American(s) slowly accumulating from other exchanges via arbitrage? Or is this just because the volume is much lower?
edit: meant bids
|
|
|
|
...
Hi crackfoo, FWIW I have made my binaries available for debian (amd64, 64bit): https://cryptap.us/uno/uno-wheezy.amd64.tar.gzhttps://cryptap.us/uno/uno-jessie.amd64.tar.gz!!!NOTE!!! These binaries are compiled with "--with-incompatible-bdb" so I'm using the version of Berkeley DB in Debian. If you care about being backwards compatible with version bdb v4.8 please backup your current wallet.dat and remove it from .unobtanium so that a new one can be created. Basically, use a new wallet.dat and move coins there to test with. I use the wheezy version for all my services and have not observed any issues. But I don't mine so if you are still running into issues it could be something in the mining rpc, block submission code or a miss-configured system. I do have a current issue with Insight explorer not understanding confirmed transactions but I am more suspicious of the general bitcoin v10 code and how Insight is working with it (lots of flux at Bitpay on how Insight will move forward). edit: changed links, clarified 64bit I'll give them a try, I use the --with-incompatible-bdb as well. Wil let you know if there is any change. hasn't crashed yet... so far so good. But wallet address changed yet again.... uKfQf7M6WX47Pt5PYatGzKcAAfgVjfoRuh cryptapus, still running with your build. Do you do anything custom with your building??? I just run: make -f makefile.unix USE_UPNP=1 USE_QRCODE=1 USE_IPV6=1 Nothing custom, just: ./autogen.sh
./configure --with-incompatible-bdb
make
|
|
|
|
Well I can cross scrambling to find Windows solutions for everyone off my list. Back to linux my love, that no one cares about.  if one were to upgrade to a new laptop, with linux or no OS at all - what would you advise recommend for a relative linux virgin? as i understand there are a lot of linux variations, TIA Hi Edgar, I see many folks suggest ThinkPad laptops for linux, they seem to have wide support and adoption. Here are a couple of links: http://www.linux-laptop.net/http://www.ubuntu.com/certification/Ubuntu appears to be well supported for beginners. I started with Debian after the old redhat (free) and missed the Ubuntu boat, but probably would have taken that route had it been available back then. Of coarse once you get far you might end up with Debian if you value orgs over companies, but that's another topic. I have been using Dell laptops for the most part. I think there is a XPS 13 that comes loaded with Ubuntu... Ah, here it is: http://www.dell.com/us/business/p/xps-13-Linux/pd(I don't work for Dell, my opinion only, yada-yada-yada...) |
|
|
|
Awesome, you're doing well! Thanks for helping piece together a look at the mining network.
yeha, I've been running 200-400+Th/s since last week. uhXrK4374zXjAQxW8TA6FRaVjXG1edcXc1 is me as well. Address keeps changing probably cause it keeps crashing and restarting so much... some attention to this issue would be nice. Hi crackfoo, FWIW I have made my binaries available for debian (amd64, 64bit): https://cryptap.us/uno/uno-wheezy.amd64.tar.gzhttps://cryptap.us/uno/uno-jessie.amd64.tar.gz!!!NOTE!!! These binaries are compiled with "--with-incompatible-bdb" so I'm using the version of Berkeley DB in Debian. If you care about being backwards compatible with version bdb v4.8 please backup your current wallet.dat and remove it from .unobtanium so that a new one can be created. Basically, use a new wallet.dat and move coins there to test with. I use the wheezy version for all my services and have not observed any issues. But I don't mine so if you are still running into issues it could be something in the mining rpc, block submission code or a miss-configured system. I do have a current issue with Insight explorer not understanding confirmed transactions but I am more suspicious of the general bitcoin v10 code and how Insight is working with it (lots of flux at Bitpay on how Insight will move forward). edit: changed links, clarified 64bit |
|
|
|
What platform or OS are you using? This sounds like a memory allocation issue, valgrind should help narrow it down. Debian wheezy. Its the only coin doing this. total used free shared buffers cached Mem: 32961880 30365640 2596240 0 445704 13651636 -/+ buffers/cache: 16268300 16693580 Swap: 523260 441748 81512 Hmmm... I'm on Debian wheezy as well, no issues like that. AMD64 I'm guessing? Any hints in ~/.unobtanium/debug.log? I am on Debian Jessie, AMD64. Boost gave me no end of troubles until I built with the flags: --with-boost=/usr/local/ CXXFLAGS="$CXXFLAGS -DBOOST_VARIANT_USE_RELAXED_GET_BY_DEFAULT=1" Not sure if this will help in your situation. I will make a VM image of wheezy and see if I can reproduce. Docs show to install the following: sudo apt-get install libqt4-dev libprotobuf-dev protobuf-compile libqrencode-dev
FWIW, on Debian wheezy and jessie I haven't had any issues with boost. I've always made sure all boost libs are installed: sudo apt-get install libboost-all-dev
One item that I do differently: ./configure --with-incompatible-bdb
as I have no concerns about Berkeley DB backwards compatibility... |
|
|
|
What platform or OS are you using? This sounds like a memory allocation issue, valgrind should help narrow it down. Debian wheezy. Its the only coin doing this. total used free shared buffers cached Mem: 32961880 30365640 2596240 0 445704 13651636 -/+ buffers/cache: 16268300 16693580 Swap: 523260 441748 81512 Hmmm... I'm on Debian wheezy as well, no issues like that. AMD64 I'm guessing? Any hints in ~/.unobtanium/debug.log? |
|
|
|
Dedicated Android Wallet for UNO - Request funds for developmentSee the original request here: https://bitcointalk.org/index.php?topic=527500.msg10831261#msg10831261We now have 160 of our 125 UNO (at today's price) goal! udroidNXd1YNoL1DgNu8NktemcnexiBByMYou have all pushed this over the top! As they say, many hands make light work. I am glad to see this community going the extra mile to show our new Android app dev. what their work means. Good luck to HashEngineering on this endeavor, you have a strong reward waiting for you. I will proceed to payout as stated in the first post on this topic, namely 1/2 at app launch, then 1/2 a month after, or after any showstopper bugs are squashed (whichever comes first). By all means if you wish to continue, or didn't get a chance to donate please do. Keep in mind that devs. with skin in the game tend to stick around. Thanks everyone for your generosity! Another update from HashEngineering via PM: I have finished some of the testing, so I moved on to creating the app. So far it is syncing. Not sure if sending and receiving work yet. Icons are also wrong. Hopefully I can get something workable to test with other users soon.
A reminder, if you want your coins back PM me with a signed message from the address you sent funds from and they will be returned. |
|
|
|
...
Are you serious? A binary supplied by someone from the internet? Who guarantees this binary does not steal private keys? Unless "Myriad's 8Bitcoder" is a trusted person, nothing from him should be published and even put on the official UNO page. And posting a virustotal.com log, is total bullshit, as it can only detect things it already knows. I can compile a Windows wallet that sends the private key to me in under 20minutes. And there will be 0 virustotal.com detections for it. FWIW, although I did not reach out to 8bitcoder I will vouch for he/she as being a talented, honest coin dev with a passion for the craft. 8bit's Myriadcoin is the first multi-algorithm (5 algo's mined concurrently) coin, even having a paragraph in Andreas Antonopoulos' book "Mastering Bitcoin". I trust 8bit, and I trust that FK received the binaries from 8bit. Not trying to advertise for it, just giving my endorsement. (Frankly, I'm a bit surprised someone was able to get 8bit to do it, kudos.) But that's the problem with binaries, at some point you have to trust someone. Otherwise you will need to review the source code and compile your own. Agreed that a more formal solution is in order. (I will say that I am paranoid and don't trust anyone so I always compile my own, even Bitcoin. Not that everyone can do that...) |
|
|
|
Which way was the decision for auxpow decided? As I was reading thru the thread about it, but I don't really have time to read thru countless pages past the 10 I already read thru about it that contained many different ideas for how auxpow should be implemented. I just need to know which way the auxpow setup is currently functioning so I can make use of it with all the stuff I am currently working like mad to configure/build.
Yeah we discussed many ideas, the decision was made to go with the traditional route, same/similar to what namecoin and others are doing. Just with bitcoin or with all sha-256 coins? I *think* just Bitcoin - at least that's what was decided. Wether the implementation is really Bitcoin specific, or would also allow other sha-256 coins I do not know. You could try tweeting @BryceWeiner about it if you're curious. My understanding is that you should be able to merge mine UNO with any coin that uses SHA256 as POW. But pools running BTC will probably dominate the difficulty. |
|
|
|
I don't want to screw up my old wallet by updating. I'm just going to take these steps... My plan is to wait for a new Windows wallet to be compiled, copy my existing wallet.dat file, install the new wallet, paste old wallet into new unobtanium wallet file. Are those the steps to get into the .0.1.0 fork?
That should work. Do yourself a favor and make a backup of everything before you overwrite, especially wallet.dat. As long as you don't have any transactions after block 600k you should be fine. |
|
|
|
|
I don't think this should be isolated to miners. I believe all transactions on v0.9.5 after block 600k will be questionable at best, on a forked chain at worst. I would advise saving your wallet.dat and waiting for a v0.10 binary to become available.
|
|
|
|
|
Show Posts
