Just unpacked my first L3+ and am reading the A4 page that came with it. It says there When powering the device up, please be sure to power the has boards first and the control board only after the hash boards have been powered. I was wondering how you guys solve this. I was thinking it was as easy as just switching the power supply on that powers control board AND hash boards and powering therefor both at the same time. Does anybody really delay the powering of the control board ? Or does this more refer to situations where multiple power supplies are used? Just want to know before I see the miner go up in flashes and smoke  Thanks for any advice in advance! |
|
|
|
It seems that the orphaned blocks you saw were just a string of bad blocks. The pool you cited, Suprnova, had 5 orphaned blocks in a row at https://bella.suprnova.cc/index.php?page=statistics&action=blocks, but the blockchain is continuing without issue elsewhere: https://prohashing.com/explorer/Bellacoin/Why that coin still exist on polo? Because all what have Bela is chess game.. which have problem to withdraw coins.. And the problem still no solved
Please check out Belacam.com, the social media site that runs on Belacoin with over 2,000 users and is actively being developed and improved. Community members are building projects on the Belacoin blockchain like a community-managed mining pool and Beladice, a virtual dice game that runs only on Belacoin. Beyond that, we have one of the largest altcoin Slack communities with almost 1,500 members in the Belacoin slack at http://Belacoin.herokuapp.com. And yes, there is also a chess app/web wallet on the Android app store that runs on Belacoin with 1,000 - 5,000 installs and a 4.2 star rating out of 67 reviews: https://play.google.com/store/apps/details?id=com.vasilkoff.wallet_bela&hl=enYou don't see a pic from hash-to-coins what I posteded ? there is 15 orphans because as I said, someone is attacking the network with 550 GH/s in that moment, I will next time make a screenshot to you with hashrate, and Prohashing in that time didn't found blocks, Prohashing in last 24h as you can see found just 19 blocks, otherwords, Prohashing and Suprnova with just 12 blocks in last 24h, they didn't mining this coin, we are talking about 30 blocks on 2 pool all day, you can not even compare that and figure what exactlly happened. I was found 38 blocks on H2C, in period of 40 min when diff was lower, witch after 50 confs became Orphans, 25 of them !! And trust me when I say, the same thing happened to Tips !! As soon as you get that sooner you will stop this attacks !! As I can see we are mining when this coin is out of profit and then when diff finally goes down, that attacker get all the blocks, so what is the point to invest in mining this coin then if we can not participate in all blocks normaly ? Stop attacks ! Read the network, follow what happened in particular time and you will get that something is fishy, somethings is wrong, some Anon is doing Selfish Mining...you can read on google a lot about that...so exactly that happened on your network wen diff is going down. Topic of Fedora coin/Tips coin about Selfish mining: https://bitcointalk.org/index.php?topic=1420302.msg15254849#msg15254849Confirmed, my last 12 blocks were orphaned. Will stay away from mining BELA until this has been dealt with. |
|
|
|
Unable to build the latest source from https://github.com/BTA-BATA/BATA-SOURCE on Debian 8/amd64: ...
bata/src/primitives/transaction.h:24:5: required from here
serialize.h:358:9: error: 'class CSizeComputer' has no member named 'write'
s.write(pbegin, pend - pbegin);
^
In file included from checkpoints.h:8:0,
from chainparams.h:10,
from alert.cpp:8:
uint256.h: In instantiation of 'void base_uint<BITS>::Serialize(Stream&, int, int) const [with Stream = CSizeComputer; unsigned int BITS = 256u]':
serialize.h:500:5: required from 'void Serialize(Stream&, const T&, long int, int) [with Stream = CSizeComputer; T = uint256]'
serialize.h:765:40: required from 'void SerReadWrite(Stream&, const T&, int, int, CSerActionSerialize) [with Stream = CSizeComputer; T = uint256]'
primitives/block.h:46:9: required from 'void CBlockHeader::SerializationOp(Stream&, Operation, int, int) [with Stream = CSizeComputer; Operation = CSerActionSerialize]'
primitives/block.h:40:5: required from here
uint256.h:278:9: error: 'class CSizeComputer' has no member named 'write'
s.write((char*)pn, sizeof(pn));
^
makefile.unix:186: recipe for target 'obj/alert.o' failed
make: *** [obj/alert.o] Error 1
Until which block height can we run the old wallet? |
|
|
|
More nodes
addnode=69.64.35.244
addnode=173.199.65.54
addnode=45.76.27.218
addnode=73.148.18.80
addnode=95.218.209.141
addnode=52.58.50.77
addnode=66.56.61.161
addnode=149.210.234.234
addnode=158.69.245.58
addnode=158.69.245.58
addnode=138.201.65.88
addnode=45.76.89.17
addnode=52.14.92.197
addnode=173.212.202.33
addnode=172.98.67.62
addnode=46.105.63.132
addnode=82.176.15.68
addnode=72.13.188.130
Since updating my node to the latest source it is "Activating best chain..." since more than 2 days: argentum-cli getinfo
error: {"code":-28,"message":"Activating best chain..."}
...
2017-04-28 09:15:55 UpdateTip: new best=3dc4d6177e28a8fd14f30e3e29294bb5f2196dd4c8064db301b8f7b551312964 height=231972 algo=1 (scrypt) log2_work=49.824046 tx=304026 date=2014-02-26 10:36:03 progress=0.105313 cache=22.4MiB(82338tx)
2017-04-28 09:15:55 UpdateTip: new best=304a336efeec42fab08a49bae1ce74836743c2f5c120bd176627906231c303db height=231973 algo=1 (scrypt) log2_work=49.824052 tx=304027 date=2014-02-26 10:36:33 progress=0.105314 cache=22.4MiB(82339tx)
2017-04-28 09:15:55 UpdateTip: new best=342d9919333048834c64421dba877aab756f2c57f8457f52cd3f11bd278abf3b height=231974 algo=1 (scrypt) log2_work=49.824058 tx=304028 date=2014-02-26 10:36:55 progress=0.105314 cache=22.4MiB(82340tx)
2017-04-28 09:15:55 UpdateTip: new best=6b1cd3c0282f1c6fad6154df25960ec182681704d1c0a8351435591bb268550d height=231975 algo=1 (scrypt) log2_work=49.824064 tx=304029 date=2014-02-26 10:37:28 progress=0.105314 cache=22.4MiB(82341tx)
... I hope it will eventually finish this process. |
|
|
|
Guys, we need nodes, the wallet does not want to be synchronized
Here you go: addnode=108.61.10.90:8007
addnode=173.168.5.106:8007
addnode=157.161.128.61:8007 HTH |
|
|
|
FWIW: I have 5 instances of C.A.T. running on a VPS w/ 2GB RAM since quite a long time and it's only Cryptopia that is giving me headaches recently in terms of hanging/unresponsive C.A.T..
maybe this is the solution for most of the challenges of CAT? for every exchange start a separated instance?anyone can confirm this? thx  From my point of view you can benefit of 1 CAT Instance/Exchange. Especially when you run a lot of markets for any exchange : if a single exchange became slow /unresponsive that slowness will damage also the other exchanges api. I wrote the possibility to log on more than one exchange with a single CAT instance but run 200 markets on 4 exchanges with 1 single CAT copy will gives you more problems than run 4 CAT instance on 1 exchange each and 50 markets each. I am running an instance for every exchange since the days of Cryptsy. When one exchange gets unresponsive or its Anti-DDoS limits your IP then it's only one exchange to reconfigure and not all. Since I only upgrade when C.A.T. crashes, I currently run 4.6, 4.7 and 4.8 in parallel. Interestingly Cryptopia is stable again with ~15 markets since I set the max 1 query per time to 250ms. Below it freezes on me and I suspect that is Cryptopia rate limiting my API calls. Personally I would see the running an instance per exchange as the recommended way to set things up, it has only advantages IMO. HTH |
|
|
|
Since CAT not a free and you have a terms which users agreed first, I think it's an absolutely normal to expect from you fulfilment of service in adequate way. i think that my support is one of the fastest here on the board and i'm sure i can compete with most of current professional services. Your support is absolutely first class and leaves no wishes open! I for one am glad I don't have to create an account in another of these piss-poor managed "it-takes-just-a-day"-forums to stay up2date wrt C.A.T. |
|
|
|
Can someone share active nodes list?
Have only one node last few days.
Here you go, though only 3: addnode=88.99.173.100:12387
addnode=96.235.143.102:12387
addnode=[2001:0:9d38:953c:30da:1e11:4d84:99fa]:12387
HTH |
|
|
|
|
FWIW: I have 5 instances of C.A.T. running on a VPS w/ 2GB RAM since quite a long time and it's only Cryptopia that is giving me headaches recently in terms of hanging/unresponsive C.A.T.. For example the instance on Bittrex is still up and running in version 4.6 as it is running since end of January.
I am not shilling C.A.T. but it does run reliably if the exchange you're on and the internet connection you use is running well and performant.
And then please do not forget that you all got an extremly innovative program with a lifetime upgrade license and personal support from the developer at no further cost.
Keep going Sampey, you do a great job and I am thankful for every new release. Though C.A.T. could indeed react more graceful to failing exchanges or exchanges with rate limiting (notifying the user when you can detect it would help - since I set api call per time to 300ms in Cryptopia it seems to keep working).
Cheers - psycodad
|
|
|
|
For a coin with so many heavy hitters this seems ignored. But also unobtainable for a person who does not mine? No exchanges?
It is traded on Novaexchange: https://novaexchange.com/market/BTC_SLM/Though you can still easily mine a few coins from within the wallet and the increase your holdings by burning and staking. HTH |
|
|
|
Nice! Thank you very much, works perfectly fine. Two little issues/small typos: - Line13[view/wallet]: There is the opening bracket for br missing
- Line96[view/wallet]: The link contains a typo: addrss instead of addr
ess
HTH |
|
|
|
I thought that the Nova Exchange was going to set the confirmation value to 100? The value still seems to be set to 999 confirmations...
+ the wallet is in maintenance again. |
|
|
|
Sorry if I missed that, but does anybody know why Novaexchange rejected Byteball addition after it made it past the voting:  |
|
|
|
I try to compile qt and failed...
In the CLI version , how i can see my wallet?
Check 'slimcoind help' for a list of supported rpc commands you can send to a running daemon. For a start check 'slimcoind getinfo'. HTH |
|
|
|
If anyone wants to take it over, id surely support them. The coin has potential I just havnt the extra time.
Franko - I see you have a new job, being a copper?  So I guess busting grandma's with busted tail lights has consumed all your freedom of time? [i kid ... but that .gif bears an uncanny resemblance] real question: Could team EXP assure that franko-net has at least 3-5 'seeder' nodes? pretty pls Yes, ill get them up, someone give me a few nodes and ill fork frk to the latest ltc code this week and get 5 nodes up. Here you go: addnode=73.211.90.130:7912
addnode=108.61.10.90:7912
addnode=[2001:19f0:300:1458:225:90ff:fe89:51aa]:7912
addnode=157.161.128.55:7912
addnode=84.242.139.4:7912
HTH |
|
|
|
Thanks for the fast answer! Unfortunately, I think the error is the same. I copy & paste the whole message in a pastebin as it's too long for a forum post: https://pastebin.com/LHD9YxV4Will see if I can get an 1.58+ Boost package in some Ubuntu 14.04 PPA. I can reproduce these errors exactly on both Debian 7 (Wheezy) and Debian 8 (Jessie) when doing: git clone https://github.com/slimcoin-project/Slimcoin/
cd Slimcoin
git checkout master
make -f makefile.unix USE_UPNP=- USE_IPV6=1
HTH |
|
|
|
does anyone have nodes for the old block chain - the one Bter is on? thanks Only one active node too and it is not a regular TIPS node, "subver" : "/Euphoria:1.1.2/" This network has no active nodes because wallets crashes when tried to create block > 1663999 exactly, I am running https://oldtips.poolto.be (very old Fedoracoin pool, up since end 2013) and i have same behavior. Daemon crash while it find block 1664000. Didn't find a way to fix it. in daemon log: 2017-03-22 09:10:10 receive version message: /Euphoria:1.1.2/: version 70000, blocks=1664000, us=xxx.xxx.xxx.xxx:54920, them=120.55.68.251:44889, peer=120.55.68.251:44889 and it crash. anyone experiencing same? I'm using https://github.com/fedoracoin/fedoracoin , branch master. The wallet tries to count the existing supply to calculate next reward and crashes with that which was expectable and I warned a few times that this will happen. The call to GetChainValue is the culprit here: https://github.com/fedoracoin/fedoracoin/blob/master/src/main.cpp#L1139A new checkpoint could help to move a few thousand blocks before the same problem occures. IIRC you could add one or two checkpoints something like 10-50 blocks before current block and it should start going again for some time. Difficult task will be to calculate the supply at this block you checkpoint. TBH the new TIPS also fails, but it fails more gracefully when calculating the supply and will just stick with 50k block reward for eternity. |
|
|
|
Finally got my wallet to sync with two or three active nodes. Seeing as the Cryptopia, Prohashing and Block-Genesis wallets are down, not sure what is updating the blockchain. Maybe Prohashing will drop Stablecoin because they do nothing but actively sell, depressing the price.
I have numerous addnodes and not sure which two or three are active. I have listed them here. Someone is mining and I will be soon.
addnode=108.186.237.29
addnode=109.121.82.231
addnode=184.171.221.204
addnode=109.80.94.251
addnode=93.138.167.14
addnode=31.207.20.162
addnode=188.126.8.14
addnode=151.80.140.87
addnode=198.143.188.42
addnode=113.162.188.201
addnode=203.59.132.204
addnode=86.22.130.144
addnode=59.167.189.49
addnode=72.84.189.238
addnode=85.217.147.117
addnode=72.78.100.8
addnode=184.185.216.85
addnode=192.99.35.133
addnode=85.236.188.28
addnode=172.110.29.94
addnode=174.69.18.39
addnode=203.20.114.252
addnode=24.4.156.63
addnode=203.20.114.252:17500
addnode=90.4.223.19:17500
addnode=95.32.113.36:17500
addnode=96.33.131.50:17500
addnode=98.114.178.228:17500
Right now my node is only connected with two other nodes, but at least I seem to be on the same chain as Novaexchange: addnode=85.236.188.28:63081
addnode=203.20.114.252:17500
HTH |
|
|
|
Did you try to increase the rpc threads, i.e. something like: in your .conf file ? HTH |
|
|
|
|
Show Posts
