|
I have successfully used the service in the past months to purchase a necklace off eBay and two omega watches, and I'll keep using them for all my next btc purchases.
Definitely recommend.
|
|
|
|
ubiqpool.io made some security changes, unfortunatelly also for API part. we made fast alternative api source, but we don't know what happens there. any contact to pool owner or some support?
version 1.1.3
- fix downloading api data from ubiqpool.io
That would be me, would you mind joining the slack so we can sort this out? |
|
|
|
I'm posting to say that ubiqpool.io has upgraded to version 1.5.9, we are ready for the hard fork! |
|
|
|
|
Very nice. Excited for this Ubiq launch.
Also i'll run a pool
|
|
|
|
As far as i can tell you do have ssl encryption but if a user goes to the page for the first time to crypto-trade.net it uses standard http. Then only after manually appending https the http>https redirection works. dunno. Tested on Safari and chrome btw |
|
|
|
|
Has been asked before, but i don't remember seeing any answers, is there any way to view hash rate in the daemon?
|
|
|
|
|
What is the default rpc port?
|
|
|
|
Is there command for viewing my hashrate in vericoind? Like gethashespersec in ltc?
try getmininginfo |
|
|
|
I think there's a minor bug. Just installed it and on the app preview version is set to $VERSION  |
|
|
|
|
Mining is possible through the coin daemon as well, right?
|
|
|
|
I've set up a test pool at 104.207.133.114I invite anyone with a rig to try it out. If you have any problems, please join the slack and get in touch with me or in the #jumbucks channel. Also, add the pool node if you can, it helps payment processing. enode://4a5b918960f5db18a5bd07b23a796c07269c5206165206ada39a6184cec476578a0a2e035d9aec034ab8061939dfd70957975e7c7e833220e9ff81d7f42430b7@[::]:30303 |
|
|
|
Ask mining pools to support JBS EE.
I'll run a pool  |
|
|
|
Compiled it on a 32 bit debian install when I get through the one fatal compile error and start it it gives me this. Jul 20 14:35:55.454 [err] tor_assertion_failed_(): Bug: src/tor/memarea.c:127: alloc_chunk: Assertion realign_pointer(res->next_mem) == res->next_mem failed; aborting.
Jul 20 14:35:55.455 [err] Bug: Assertion realign_pointer(res->next_mem) == res->next_mem failed in alloc_chunk at src/tor/memarea.c:127. the compile error is in net.ccp line 65 should be boost::array<int, THREAD_MAX> vnThreadsRunning; instead of array<int, THREAD_MAX> vnThreadsRunning; I had to upgrade boost to version 1.6 else it would not compile due to SSL3 not compiling. Please provide a pre-compiled 32 bit linux version. Nice whoever incorporated this tor stuff just dumped a preconfigured source for 64 bit in there without even considering that some people would like to run it on w 32 bit system.
Please get rid of the tor stuff it only gets in the way of good staking. The latency is too much for a staking coin.
I can tell you that when i had a pi2 (32 bit arch) i couldn't compile the wallet and i came to the conclusion that the tor stuff didn't run on 32 bit arch There are plans to remove tor as soon as the next update. |
|
|
|
the problem is the chain is shattered and everyone forked probably
Possible, but I got three connections and and it looks like we're all sitting on the same block. Since we seem to be at a dead end, i say we liquidate the SRF between coin holders. We snapshot the chain at block 34761 and we divide the btc equally between the remaining coin holders. If there are technical problems i can bring in a dev can we can pay him some % out of the srf. Then again, if you guys are willing to restart the chain and go from there i'm in for that too. |
|
|
|
|
the problem is the chain is shattered and everyone forked probably
|
|
|
|
|
A swap would be necessary, we need to leave the bulky CON to rest in peace, but i would only like to see one if it's done in a good way, like using a chain parsing method, that makes it fair and transparent, allowing people to redeem their coins without deadlines.
|
|
|
|
|
We would really need a IOTA unit specification, even just two lines in a text file to go with the IRI source code, that explain how the measurements go as to avoid any misunderstandings.
|
|
|
|
|
Show Posts
