Any word at all on Cryptopia wallet?
The last reply I got, was this one few days ago: We are just worried as it seems that there are different forks in the wild. If you can give us some nodes that are on the correct fork then we will add them and look at taking the wallet out of maintenance.
Our main concern is that users with 8bit may want to withdraw to another exchange, if that exchange is on the wrong fork then it results in an awkward situation and cost for our support staff.
If you can confirm that the major exchanges trading 8bit are on the same as fork as us, while also supplying the developers supported nodes then we will, in good faith, update and take the wallet out of maintenance.
For the peace of mind of our developers it might best if the 8bit Dev is able to send us some confirmation and nodes to my email - <email address here removed by drays for security considerations>. I will still push this but the more info we have, the better!
Any questions please let me know.
I replied with the links to node information published in this thread, and the link to the official block explorer. Also I notified the developer, so he could additionallt send the needed info to Cryptopia directly. Since that, I have no news from anybody. Not sure whether Cryptopia got the needed info from the dev or not. But in fact, the info publushed here on the thread is more than enough. One serious possible obstacle could be the fact that the official block explorer at http://explorer.8-bit.ga/ is usually behind real time, and currently is 3 days behind. I don't know what else could I do  Did anybody have any other contact with Cryptopia lately? In any case, whatever you write them, please DO NOT accuse them of staking the funds. Those accusations are insulting and are completely unproven, and they could do nothing but harm. I contacted them yesterday and all I got was the standard response stating that the are investigating a fork. Even though I requested that they not give me the boilerplate answer that there working on investigating a network fork, that's still the only response I got. I can understand that they may be working on something, but if I request a status and specifically ask for them to let me know exactly what's going on, and all they do is give the same crappy, uninformative answer they've been giving... makes me wonder what's up. I didn't accuse them of anything, just asked for a detailed status, the current plan and any possible eta... got NOTHING in return. |
|
|
|
|
Any word at all on Cryptopia wallet?
|
|
|
|
Seems to be working to me. |
|
|
|
|
Can anyone get a wallet to sync? I have tried both a linux and a windows wallet and they never sync... just sit there. Is there a new wallet version out?
|
|
|
|
|
If anyone is running multiple nodes off the same ip, would love some help.
|
|
|
|
I have an Eternity node. ROI is horrible, keeping it, but Das is tons better.
well now i have an Eternity and a Das running Head to Head so lets see who wins after a week  Excellent! Would love to compare results after a week or so! |
|
|
|
|
I have an Eternity node. ROI is horrible, keeping it, but Das is tons better.
|
|
|
|
|
Anyone have a guide for running multiple MN's on a Linux system (not on a vps, but my own system)?
|
|
|
|
We have managed a return of Bittrex to the longest chain. They are re-pushing rolled back transactions at the moment. When they officially re-open their wallet, I will contact Cryptopia to find out what's going on there.
Besides I still have no clue why they locked the wallet, why people from our community ask them to re-sync, etc.
Thanks! Please keep us up to date on Cryptopia. Been waiting to get my coins out of there for a week. |
|
|
|
|
Where is the best place to get DAS?
|
|
|
|
I have also contacted Cryptiopia concerning the wallet being in maintenance. Here is there reply: Sender: MrFloppy7/22/2017 12:18:37 AM Hi robert3harrison, We are not sure when 8BIT will be back up and running as there currently seem to be several forks. We have some new nodes and are in the process of re-syncing the wallet. We are not sure exactly when this will be completed. Any questions or concerns please let me know. You can check back to see when this issue has been resolved and the wallet put back online from our coin info page here - https://www.cryptopia.co.nz/CoinInfo/?coin=8BIT&view=settings Thanks, Cryptopia As a followup... while I didn't sync from "scratch" (I used the bootstrap, which Cryptopia says they can't do), once I got everything running right, the sync went quite fast. Even syncing from scratch, I don't think it should take more than 24 hours. Not sure what Cryptopia is waiting on. |
|
|
|
Hi Guys, is there any guide or tutorial to setup a linux MN?
Thanks in advance
This was on the Slack Channel: This is the instrucions I am following to build the 8bit software. I am using Ubuntu 16.04 on a Amazon AWS EC2 instance (since it is free for a year :slightly_smiling_face: ) I am unfortunately not through the building process, since I am having problems building the file rcprawtransaction.cpp. mkdir <directory you want this to live in> cd <that directory> sudo apt-get install build-essential libssl-dev libdb++-dev libboost-all-dev libqrencode-dev libminiupnpc-dev git clone https://github.com/bitcoin/secp256k1.gitcd secp256k1 git checkout a1d5ae1 ./autogen.sh ./configuremakes udo make install sudo ldconfig cd .. git clone https://github.com/8bit-dev/8bitcd 8bit/src/ mkdir obj/crypto make -f makefile.unix -j2 strip -s 8bitd mv 8bitd <where ever you want it to live> mkdir ~/.8bit mv boostrap.dat ~/.8bit Should get you started. GL. |
|
|
|
|
Used the bootstrap and nodes specificed that are working, but I'm stuck at block 974632
My log file currently looks like this (last few lines):
ProcessBlock: ORPHAN BLOCK 57, prev=5d287216797d200819c6b63735f9016b5446b47a44ec71a965a08d1911269051
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 144.76.115.195:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 46.101.15.38:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 94.226.187.230:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 144.76.115.195:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 46.101.15.38:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
SetBestChain: new best=5fb1dcb3f7d70cf54c7e6151caa62e4752ffc6f9cc72ea06ae906c211c84a635 height=974633 trust=30895760552085056363 blocktrust=4042435328510 date=07/15/17 14:04:32
ProcessBlock: ACCEPTED
ProcessBlock: ORPHAN BLOCK 58, prev=57260aa1549d6e20608ed6b5608ae48e0a14a4ee8a767d492d66eb3333952321
ProcessBlock: ORPHAN BLOCK 59, prev=6936f293a6114427625f4d6d5d2e6cb0449f423b9d9fed22904b91c8c0104977
connect() to 46.101.206.55:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 144.76.115.195:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 213.249.13.246:18888 failed after select(): Connection refused
connect() to 46.101.15.38:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 144.76.115.195:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 46.101.15.38:18888 failed after select(): Connection refused
Anything I can do here?
|
|
|
|
|
Is it ok if I send more than 112 coins to run MN?
|
|
|
|
Can anyone confirm that it is ok to send coins from Cryptopia?
With the blokchain that he has shared I have been able to receive the cryptopia coins of July 15, which confirms that their nodes are in the cryptopia chain, with the first group of nodes synonymous but did not receive my coins. I mean I have confirmed that the second group of nodes are in the correct chain osea the same as cryptopia Ok, thanks. Will update .conf file to the second group of nodes and send from Cryptopia. Thanks again for the help. |
|
|
|
|
Can anyone confirm that it is ok to send coins from Cryptopia?
|
|
|
|
|
Anyone know the best place to get coins and be able to send them to wallet?
|
|
|
|
|
So is it safe to transfer coins from any exchange Cryptopia? I don't see 8bit on Bittrex, am I wrong?
|
|
|
|
|
So after running the wallet for over 14 hours... basically getting nowhere. Am downloading the snapshot. What should be in the .conf file?
|
|
|
|
Trying to compile the gui wallet on linux ubuntu system and getting an error. Is there anyone around that can help?
What's the error? Running the following in: qmake (runs fine) make (gives below error): src/key.cpp: In member function ‘bool CPubKey::Derive(CPubKey&, unsigned char*, unsigned int, const unsigned char*) const’: src/key.cpp:730:69: error: ‘class {anonymous}::CSecp256k1Init’ has no member named ‘ctx’ bool ret = secp256k1_ec_pubkey_tweak_add(instance_of_csecp256k1.ctx, (unsigned char*)pubkeyChild.begin(), pubkeyChild.size(), out); ^ make: *** [build/key.o] Error 1 Have you installed secp256k1? Following something similar to : cd ~&&git clone http://www.github.com/bitcoin/secp256k1&&cd secp256k1&&git checkout a1d5ae1&&./autogen.sh&&./configure&&make&&sudo make install&&cd .. Did everything except was missing the git checkout a1d5ae1. Compilation now continues...stay tuned (lol). Hello, have you fixed the problem of synchronization of the chain? Is your wallet in sync? Wallet now up and running and appears to be syncing. About 2 years to go. Will update later as to it's progress. |
|
|
|
|
Show Posts
