Show Posts
|
Pages: [1]
|
If you are miner please make sure that you are mining on pools that are running latest wallet version (0.13.5) or your rewarded coins will not be spendable on exchanges.
Shameless self promotion: https://emc2.pool-mining.xyz/ is on the 0.13.5 wallet and on the correct chain. You can safely mine there, i'm also monitoring it like a hawk until all the mess has cleared up a little. Also, feel free to use the bootstrap at http://bootstrap.0x03.services/einsteinium/EMC2.html to get back onto the right chain quicker. Please make sure to join the related Discord server to be up to date. Have a nice day.
|
|
|
hi everybody. am i right to assume, that by issueing $WHATEVER-cli decodescript 0100010188 you will essentially get a valid burner p2sh address for not only bitcoin but probably any p2sh supporting coin? The results from bitcoin-cli: # bitcoin-cli decodescript 0100010188 { "asm": "0 1 OP_EQUALVERIFY", "type": "nonstandard", "p2sh": "38e6tUuroVTeG5vSdoB3bBSa4AaKVJxzr2", <- see here [...] }
In order to be able to spend coins sent to that address one would have to a) come up with a solution to '0 1 EQUALVERIFY' (how?) or b) do a (probably not well-received) hardfork implementing a special rule to allow '0 1 OP_EQUALVERIFY' to be evaluated to 1. Is that correct? Can somebody enlighten me? If anybody reading this would like to play around with opcodes and is a bloody beginner like i am, https://siminchen.github.io/bitcoinIDE/ is a great resource. Thank you, author of that.
|
|
|
What am i missing here?
zpool has too high worker diff for these to work.. they just time out. Thanks for your answer. So do i understand this right, even if i throw 12 (like i do) or 1200 MLDs at zpool, they won't get any work?
|
|
|
Is anybody pointing his MLDs at zpool? YES I AM USING #skipcbcheckcommand: # bfgminer --scrypt -o "stratum+tcp://scrypt.mine.zpool.ca:3433/#skipcbcheck" -u <wallet-addr-removed> -p c=<symbol-removed> -S ALL --set MLD:clock=796 and i get a fuckton of these: Pool 0 is sending mismatched block contents to us (X is not Y-Z) Pool 0 is issuing work for an old block: <hash>
i seem to get close to 0 shares. and when i just throw the MLDs at suprnova or hashfaster, it works as expected, with these very similar commands: # bfgminer --scrypt -o stratum+tcp://emc2.suprnova.cc:3366/ -u <username-removed> -p <password-removed> -S ALL --set MLD:clock=796 # bfgminer --scrypt -o "stratum+tcp://hashfaster.com:20003/#skipcbcheck" -u <wallet-addr-removed> -p c=<symbol-removed> -S ALL --set MLD:clock=796
What am i missing here? Thanks. Also: do these little guys get quite hot then? the hub i ordered has an Aluminium body hopefully help with heat dissipation
Mine came with heatsink and fan. This will work fine up until clock=796, to my experience.
|
|
|
sorry had a bad night thanks for the response, same architecture as a pi really was hoping some pi users were about
here's a raspi user, currently driving 3 moonlander2 and an old rpi2 for bfgminer off a 'rather pricey' and very powerful USB hub at 796, above they become unstable in a rather unpredictable way. i suspect the usb WLAN dongle i have to use in my setup as a part of the problem - i think i read about USB bus saturation being a possible problem SOMEWHERE, but didn't debug in this direction any further yet... anyways, the basic setup worked like a breeze. plug your MLDs in, run bfgminer as described in a lot of places, watch your MLDs have fun. however 9 more moonlanders are on their way to me, and i am eager to see if i can drive all i then have reliably with a bunch of hubs and one rpi3, which will eliminate the need of a seperate dongle. considering that could actually fail, i have a bunch of rpi2 around, and a bananapi routerboard (BPI-R1). i'm kinda sure i'll find a way to make it work reliably, somehow. shameless self-reply: the 3 ASICs run stable at 900, when i point a fan at them. it's not USB bus saturation, it's temperature. waiting for the rest to arrive today, hopefully.
|
|
|
sorry had a bad night thanks for the response, same architecture as a pi really was hoping some pi users were about
here's a raspi user, currently driving 3 moonlander2 and an old rpi2 for bfgminer off a 'rather pricey' and very powerful USB hub at 796, above they become unstable in a rather unpredictable way. i suspect the usb WLAN dongle i have to use in my setup as a part of the problem - i think i read about USB bus saturation being a possible problem SOMEWHERE, but didn't debug in this direction any further yet... anyways, the basic setup worked like a breeze. plug your MLDs in, run bfgminer as described in a lot of places, watch your MLDs have fun. however 9 more moonlanders are on their way to me, and i am eager to see if i can drive all i then have reliably with a bunch of hubs and one rpi3, which will eliminate the need of a seperate dongle. considering that could actually fail, i have a bunch of rpi2 around, and a bananapi routerboard (BPI-R1). i'm kinda sure i'll find a way to make it work reliably, somehow.
|
|
|
very complicated for my small brain.
it's not exactly off-the-shelf technology. i myself am still running into problems with trades a lot of times, but thats mostly caused because BarterDEX does not have this many of users yet. Basically, for a 'heads up' that is brutally incomplete and probably also a bit hilarious (but it should enable you to trade): Whenever you send coins to BarterDEX, no matter what currency, don't send one large transaction. For example, when i send in 100 xCoin, i'd usually send 10, 12, 1, 10, 12, 1, rinse, repeat ... and then whatever is leftover. This has to do with the UTXOs BarterDEX uses. I'm absolutely not fully understanding it (i'm not a dev), but by sending in multiple smaller batches in a relation of 1 to 1.2 to 0.1 i get a lot of good results and working trades. I THINK that should be the most encountered problem, that people simply cannot start trades they see due to not enough UTXOs of the right size. Of course you can withdraw your coins back out. Should it say that you don't have a matching deposit despite your balance being greater than what you've entered, lower or raise the number (try around the sizes you've sent in to fund the address, i.e. 10). Remeber, with xCoin (because it has to be added in native and not in electrum mode), BarterDEX talks to your local xcoind, so you never actually lose control and ownership over your coins. Report back with errors you get, i will try to provide assistance.
|
|
|
Hi everybody, i have basically already added xCoin to BarterDEX ( https://komodoplatform.com/decentralized-exchange/) and submitted a pull request for the BarterDEX GUI ( https://github.com/KomodoPlatform/BarterDEX/pull/151). I am running 2 BarterDEX nodes with xCoin enabled now. All i'm missing to confirm that it's working is a small amount of xCoins, like 2-3 tops. Can anybody help me out here? You can send some to xNLxNEou8QFnnNNvLfhCcxo3EAxoxTuWfEGREAT NEWS!>>>>>>>>>>>>>>>>>>>>>> SWAP completed! 1122752382-3188422727 {"expiration":1520818803,"tradeid":3414799922,"requestid":1122752382,"quoteid":3188422727,"iambob":0,"Bgui":"","Agui":"nogui","gui":"nogui","bob":"XCOIN","srcamount":0.30673471,"bobtxfee":0.00010000,"alice":"KMD","destamount":0.10000000,"alicetxfee":0.00001000,"aliceid":"10942082969801195521","sentflags":["alicespend", "bobpayment", "alicepayment", "bobdeposit", "myfee"],"values":[0.30683471, 0, 0.30693471, 0.10002000, 0.34527654, 0, 0.00012870, 0, 0, 0, 0],"result":"success","status":"finished","finishtime":1520803445,"bobdeposit":"ae2165610a6c625cfe527534c43fce685a7f7a93a1af5b1a3c68a02f919a5516","alicepayment":"bd671d81ba30850ea24d8558e4983efafe9b4ce9b4fe42dc34988cf9eb97faff","bobpayment":"5caea46d05c952b47710f2e1e4b86bc9ccd9bcde10323d928116b0a3b2e570d4","paymentspent":"1ca4b9fb23e60018960d0e7d782a2b5a7a19f81106e0f63b09a00f9b2c77d8a8","Apaymentspent":"0000000000000000000000000000000000000000000000000000000000000000","depositspent":"0000000000000000000000000000000000000000000000000000000000000000","method":"tradestatus","finishtime":1520803445}bobdeposit http://xcoin.ddns.net/tx/ae2165610a6c625cfe527534c43fce685a7f7a93a1af5b1a3c68a02f919a5516alicepayment https://kmd.explorer.supernet.org/tx/bd671d81ba30850ea24d8558e4983efafe9b4ce9b4fe42dc34988cf9eb97faffbobpayment http://xcoin.ddns.net/tx/5caea46d05c952b47710f2e1e4b86bc9ccd9bcde10323d928116b0a3b2e570d4So far, 0x03
|
|
|
|