I'll message you tomorrow when I'm available (around 12:00 in GMT-4), if it hasn't been fixed. I'm going to try Ov3rload's approach, as I haven't been specifically linking to krb5. I've been linking to libcurl fine, I'll try an explicit link to ssl on 6.5
|
|
|
Why not change to just one giant pool, sort of. What about making an altcoin as a prototype, in order to test the viability?
|
|
|
A rar file? Really? And what language is it in? (Batch? Bourne-again shell script?)
|
|
|
Is it OK if I try that tomorrow afternoon? Unfortunately, I'm going to be busy tonight and tomorrow morning.
|
|
|
I've tried and failed so far, I'll be trying later on. If anyone can solve this and wants to share the bounty, I'll explain the situation: curl compiles on both versions with --enable-static and --disable-shared, check openssl compiles on 5.5 as static; 6.5 has an existing openssl-static package that appears to be valid kerberos compiles on both as static. However, the compilation of cpuminer itself fails. 5.5 can't link to Kerberos, 6.5 can't link to -lcrypto As a last resort, Statifier might be possible, but it currently has a few disadvantages, so I'm still seeking to obtain a true static build. Specifically, if the goal was performance, then Statifier is not possible as code is still position-independent.
|
|
|
There's a bit of a dilemma in all arguments involving any sort of IP address. Bitcoin is designed so that it can function over any sort of (untrusted) communication medium. Blocks get from point A to B, verified at B, yada yada. This could be by HSMM (which identifies by callsign), satellite, even carrier pigeon in the most hypothetical of situations.
|
|
|
For English speakers out there, is this still open, or has it been claimed in the posts above? If it is open, I am willing to do this.
Thanks, could you PM me if that happens, and I don't notice here? I try to monitor threads I've posted to recently using the forum tools but sometimes I don't get a chance to track everything.
|
|
|
To clarify, are you working on an altcoin by forking an existing one? Or something completely new? If the latter, preferred language for implementation?
|
|
|
Interested, make an offer of hourly rate. Available this thursday, friday for most of day in GMT-4. I am fairly skilled with Java, 15K user on Stack Overflow with focus in Java. I am not skilled with Jpype but can read up on it before helping you. In a worst-case scenario if something doesn't work through JPype, I can do it on the Java side and have Jpype invoke that, so I am certain in my ability to handle any issues. It would be good to know which library/libraries you have in question. Skype is probably not workable (I use Linux and haven't gotten Skype working reliably), but IRC (private live message, or private channel) should be fine.
|
|
|
For English speakers out there, is this still open, or has it been claimed in the posts above? If it is open, I am willing to do this.
|
|
|
Actually, they mention that they are provably fair if you look carefully for the link on the page where you submit the captcha and roll. A hash is calculated based on client and server secrets and agreed nonces, of which part is taken to yield a 32-bit unsigned integer, which is divided by 429496.7295 and supposedly rounded up.
|
|
|
Did you just link to a non-bitcoin-related video?
|
|
|
What site? And how much do you really make JS-mining?
|
|
|
Yes, you could get it hooked up, but you wouldn't get a connection to a pool. Once you get in, set the networking settings to match your router's actual properties (i.e. some Belkin routers allocate 192.168.2.0/24 to their DHCP pool, so in that case you'd set the miner's IP 192.168.2.99 and subnet mask to 255.255.255.0)
Default gateway is nearly always router IP
|
|
|
1 Point 46 Quindecillion Let me provide more significant figures in my wording: One quindecillion, four hundred sixty-one quattuordecillion, five hundred one tredecillion, six hundred thirty-seven duodecillion, three hundred thirty undecillion, nine hundred two decillion, nine hundred eighteen nonillion, two hundred three octillion, six hundred eighty-four septillion, eight hundred thirty-two sextillion, seven hundred sixteen quintillion, two hundred eighty-three quadrillion, nineteen trillion, six hundred fifty-five billion, nine hundred thirty-two million, five hundred fourty-two thousand, nine hundred seventy-six. Or, http://tts.imtranslator.net/TYni
|
|
|
If it is a fork, then is someone's double-stating a fact not concerning enough?
|
|
|
Have you counted the posts by hand?
|
|
|
Is the maintenance of this thread not a community effort?
|
|
|
Apologies, I take that back then.
|
|
|
If the transaction was not picked up by a miner (malformed, fee too small), then eventually nodes would "forget" it by removing it from their memory pool. Your wallet would recognize this situation and would allow you to re-spend your coins, as otherwise once any coins are sent they would become unspendable by that wallet if they never got confirmed.
|
|
|
|