 Show Posts
|
|
Pages: [1] 2 »
|
It occurs to me that people may still have their coins on MintPal and need an Emoticoin wallet to withdraw to. Or maybe you just want something more powerful than the windows gui client. To set up your own command line Linux EmotiCoin wallet online, here is a simple how-to: - Google for a Digital Ocean promo code. Usually you can get $10 off.
- Sign up here for an easy to use VPS: https://www.digitalocean.com/
- Create a $5/month droplet for Ubuntu 14.04 x64
- Sign in as root with ssh (PuTTY for example), and paste in the following code:
sudo fallocate -l 4G /swapfile;sudo chmod 600 /swapfile;sudo mkswap /swapfile;sudo swapon /swapfile; sudo echo "/swapfile none swap sw 0 0" >> /etc/fstab
echo 'export EMOTICOIN=$HOME/emoticoin/src' >> .bashrc
export EMOTICOIN=$HOME/emoticoin/src
echo "alias stop_make='cd $EMOTICOIN; ./emoticoind stop; make -f makefile.unix'" >> ~/.bashrc
echo "alias start_tail='cd $EMOTICOIN; ./emoticoind -daemon; tail -f ~/.emoticoin/debug.log'" >> ~/.bashrc
sudo apt-get update
sudo apt-get upgrade -y
sudo apt-get install -y libboost-all-dev libminiupnpc-dev miniupnpc make libdb++-dev git tmux g++ libssl-dev pwgen
The first line gets you a swap file so you won't run out of memory while compiling. The rest of it is aliases and installing dependencies. Now type so that you will have a tmux session going. Then use this snippet to grab the source, compile it, and create a simple emoticoin.conf: git clone https://github.com/emoticoiners/emoticoin
stop_make
mkdir ~/.emoticoin; echo "rpcuser=emoticoinrpc
rpcpassword=`pwgen -s 44 1`">~/.emoticoin/emoticoin.conf
start_tail Now you will be watching it boot up and sync with the network. Since we used the emoticoiners fork instead of the official repo, we should have good seeds for it to bootstrap the network with. When you get bored of watching the logs, you can ctrl-c to get out of this live view of the debug log, or hit ctrl-b c to create another tmux window (google tmux for more info on how to switch between tmux windows and so forth). In either case, you will end up in the emoticoin/src directory. You can type for a full list of command line api calls. Since it is in a tmux session, if you disconnect you can always use to get back to it. If you have a windows gui client, you can export your private keys (I forget how) resulting in a long string starting with an M. To add this to your linux wallet, use ./emoticoin importprivkey <private key> If you want to output a private key (e.g. to print out in case your wallet crashes, or migrate your coins to a different wallet without a transaction), use ./emoticoind dumpprivkey <address>. Addresses in emoticoin start with a 6, currently, due to a typo in the original source. I know how to change the code to allow it to start with an E instead, however there is a risk of wallet corruption if people upgrading don't know what they are doing. So instead my plan is to provide a tool that acts as an overlay without affecting wallets. This gist shows how the basic transformation can be done with a nodejs library called coinstring (from the cryptocoinjs project). |
|
|
|
I have 500 million EMO send me any BTC you like, but do the payment first. So contact me in private if you want to.
Okay, I have sent you a PM. I can see that the withdrawal limit of 50000000 that Mintpal has is going to be a headache as it will require 10 transactions to complete (and you have to click a confirm link and wait several minutes each time). I sent them an email requesting to remove the limit or increase it by a factor of 10. If you have your coins in an emoticoin wallet of your own already, shouldn't be a problem. Edit: Apparently EMO has an 84 million coin limit hardcoded in, so increasing more than that is not possible. Currently, the max has been changed to 80 million. However, I currently have some code I am working on for the next hardfork, and it will have 990 million as the limit instead. It will also have target interval set to 1 minute. Needs some testing/review. Anyone who wants to get in touch, I am in #emoticoiners on freenode. |
|
|
|
|
Mintpal has removed EMO from the LTC market. They told me when I emailed that they will most likely never add it back because the blockchain remained dead for several weeks last month, and it "hasn't done anything special" since it started. All of the other exchanges listed on the emoticoin website have dropped it as well.
I am retaining some small hope for this little coin despite its tarnished reputation. So if anyone is selling, I am interested in buying in BTC at a ratio of 10 billion to 1 (i.e. I will pay 1 satoshi per 100 EMO). PM me if interested. I can buy up to 1 BTC worth, first come first serve.
You will be able to withdraw from MintPal for 2 weeks. However, transactions will probably be extremely slow to confirm in the mean time so they will have zero confirmations for hours, perhaps days, maybe forever. To get around this, I will give you an emoticoin address to send to and you can withdraw straight to it (or send from your wallet). Once the transaction is out on the network, I will check the quality of the transaction to make sure there is no funny business, and send you the corresponding bitcoin amount after that.
I'm planning to set up a forum, and possibly even an exchange for this coin. If you think that is a worthy goal, you can send some EMO to motivate me at:
6F2bAPuyG1qESEQPdiF3SBWcvQv53KzthQ
|
|
|
|
I found an IP that new users can connect with: 107.170.61.190Use as follows: ./emoticoind -connect=107.170.61.190 Only needed if your wallet does not get any blocks. Sorry but no, neither seed node in the source works, last I checked. To test, you need a blank system that has not been on the network in the past so that other nodes have no record of it. For example, spawn a droplet on Digital Ocean. My suggestion was harmless enough as a one time thing because the IP is one of the pools you endorse on your website (emo.miningglobalwarming.com) and I had tested it to work fine. However -addseed would have been a better choice in retrospect. |
|
|
|
Please help me, my wallet don't sync...any new nodes?
Try adding this to your emoticoin.conf: It should then download all the blocks. |
|
|
|
Fuck ! I saw many peers in my client that are still on 0.8.6.1 and I'm on 0.8.6.3. So what the fuck do I do now ?
getinfo will tell you how many blocks there are. There should be 50105 50106 now. If that is the number you see, you are good. getpeerinfo tells you what versions the clients are at. The majority should be 0.8.6.3. If not, I believe restarting the program gets you different peers. I think the danger of bad blocks being accepted is only there when most of the clients are 0.8.6.1, which is no longer the case. However, the programmer could probably have prevented the issue by use of protocol version numbers (70002 -> 70003 in version.h) if I'm understanding the code correctly. That would have made sure the new peers automatically reject the old peers messages. |
|
|
|
That aint the latest. I'm talking about the one Kreibich or whatever the fuck is the name of the founder posted in big fucking bold red letters. The new one he is bragging about in his past replies. He never linked the new one and kept blabbering about it.
That's the one he is talking about. There isn't a newer one yet. There are still a bunch of people who haven't updated to it yet, and that is polluting the blockchain and creating forks. There are two bad forks that I know of. One of them is the one reported by blocks.emoticoin.org, which the dev needs to fix. You can tell because it shows the wrong reward for blocks 50102-50111. The other one is the one I see in debug.log with 50149 blocks, where all the clients that report it say they are version 0.8.6.1. The real blockchain is the one with (currently) 50105 blocks. See here. I tried mining on the pool, I gained shares, but I never received a fucking payment. Nothing happens. Pool is fucked up too. There is no correct fucking chain, this is fucking frustrated, I'm getting 8 fucking connections and I can't even fucking mine.
Yeah I am in the same boat, thousands of shares but no payment. I think the reason is because the pool has not solved a block since I started with it. Blocks are currently being solved 1 every 3 days, since hardly anyone is mining. The fact that it takes 1440 blocks to adjust is the core problem there. |
|
|
|
this coin was a joke, i mined like 60m in one minutes, how can you take it seriously
cap too high block reward even higher
Not a bad haul for a minute. What was the difficulty at when you did that? |
|
|
|
Where's the new fucking wallet ? There's no link for that anywhere on your threaad nor on your website either !
Latest version is v0.8.6.3-g88e2a2e-beta. It is a few months old. It's linked to on the website, here. If you are a windows user it is the binary download at mega.co.nz. For Linux, use the github source. |
|
|
|
I found an IP that new users can connect with: 107.170.61.190Use as follows: ./emoticoind -connect=107.170.61.190 Only needed if your wallet does not get any blocks. |
|
|
|
what is the last version of wallet ?
i have v0.8.6.3-g88e2a2e-beta
block : 50104
That is the latest version, same as if you download from the website. You are good to go unless/until another hardfork comes out (later). |
|
|
|
|
I can't understand why miners are necessary to sync. They are only needed for new transactions to go through. It should only be necessary for the person running the client pointed to by the source code (seed0.emoticoin.org or seed1.emoticoin.org) to have the correct client running with an up do date blockchain.
|
|
|
|
Epic Photoshop skills on that new logo.  Thanks  Retargeting every block should work too, several coins do that AFAIK. I'm not a coin dev, but that requires a hardfork, no? Sounds like we need a hardfork then to get the ball rolling again. Is the Dev up for it? |
|
|
|
I have designed us a better graphical logo to use: :-) |
|
|
|
I just got the source from github. When I run, I get errors like this in the debug.log: 2014-06-15 05:41:36 trying connection 46.234.101.198:6660 lastseen=134.2hrs
2014-06-15 05:41:36 connect() failed after select(): Connection refused
2014-06-15 05:41:37 trying connection 185.5.226.70:6660 lastseen=92.3hrs
2014-06-15 05:41:37 connect() failed after select(): Connection refused I guess that means it cannot find any peers to download the blockchain from. The mining reward system needs fixed so that this coin can be usable. As others have said, it is not retargetting quickly enough. If people are not mining, that should automatically make the difficulty low enough that it is profitable to mine without much hardware. Digishield has been proposed, but that is hundreds of lines of code. Why not simply take the line: static const int64 nTargetTimespan = 1.0 * 24 * 60 * 60; // EmotiCoin: 1.0 days And replace it with: static const int64 nTargetTimespan = 1.0 * 60; // EmotiCoin: 1.0 minutes Or something like that? 24 hours worth of 1-minute blocks represents significant opportunity cost for miners. It is a lot bigger number than bitcoin's 6 hours worth of 10 minute blocks. |
|
|
|
Exactly. They don't rip the cells to shreds. They vitrify them. It's like plasticizing. You guys should read up on the newer technology for cryonics. You sound like stock market guys trying to comment on bitcoin :-)
Did they manage to put a human into cryogenic stasis and revive him again without killing the human? If so: Wow cool, I imagined many other great things being realized WAY before that (such extreme celluar rejuvenation techniques, quantum computing and cold fusion). No, that's not what he is saying... Vitrification is still a one way trip for now, even for animals. But it does prevent ice formation entirely, so the chances are not anything as bad as being ripped to shreds. And the cryogenic state is very stable, so it is likely (given good organizational policies and/or survivalist tactics) that it would be around for hundreds of years. To the people of the future where there are extreme regenerative techniques available, you would be considered essentially a living person if your brain is recoverable. (Full body replacement and reversible cryostasis would be everyday things for them, so there's no reason to think you are dead.) However, you don't want to rely on morality alone so you would want to save some money aside in a form they cannot touch without first reviving you. There is definitely room for improvement in the tech, and I've been advocating within the cryonics community that there be more focus on research. But mainstream scientists don't take cryonics very seriously, so there is a smaller pool of candidates to work on the neural cryobiology aspect. Some well placed bitcoin prizes might help get people to look deeper into the unsolved problems of cryonics. I would recommend focusing on the blood brain barrier and on cryoprotectant toxicity mechanisms. We could get to a point of perfect brain preservation within our lifetimes. If that happens, screw the rest of the body... If I had unlimited money, I would want to build a big huge storage facility (monolithic dome for energy efficiency and stability) and start cryopreserving people globally for free. 50 million people die per year, and there will be more as the population ages. With a big enough storage container, it gets really cheap/energy efficient because you only have to insulate the outer surface. |
|
|
|
Please don't go inventing your own cryptography when it can be avoided. Scrypt did the work to write up an extensive analysis of their effort, and it was reviewed by many people at great cost. And even then the result has not been totally criticism free ( http://eprint.iacr.org/2013/525). I understand that new crypto has to go through a complicated vetting process to be trusted, and there are good reasons for this. I am just curious as to why something simpler was not settled on in this case. Unnecessary complexity is not our friend. With a quick glance at the shape of your implementation, it could have trivially failed to be memory hard at all had you appended instead of prepending. I expect that it's actually spending all of its time shuffling around strings, and that a gpu implementation of it would still end up being a zillion times faster... Lower level code that preinitializes the byte array and moves the pointer down with each iteration could eliminate string-shuffling in software. (I don't know what Python is doing when it prepends -- maybe it's all linked lists or something.) Why would a GPU implementation be faster? Yes, Scrypt also put high pressure on CPU cache.
Can you elaborate on this? I couldn't find anything in the scrypt paper, or its Wikipedia article regarding "high pressure on the cpu cache". What does that even mean? |
|
|
|
I have been thinking about a possible algorithm for key derivation, for use with brainwallets and so forth: import hashlib
def derivekey(passphrase,rounds=1024):
def getdigest(x):
return hashlib.sha256(x).digest()
concatenation=getdigest(passphrase)
for i in range(rounds):
result=getdigest(concatenation)
concatenation=result+concatenation
return result
print derivekey('this is a test').encode('hex') It simply applies sha256 a bunch of times while prepending results to expand the size, with the final result being based on the whole series (as is the case with each intermediate result). This is an extremely simple algorithm, but as far as I can tell it seems to be just as useful as scrypt (which is more complex). The succession of digests each rely on the presence of the past ones, so it has to be done sequentially, and has to use up memory. Am I missing something critical here? |
|
|
|
On Arch Linux, these are installed like so: I get an issue where it displays the following error at the top of the screen, and does nothing when I type help: ERROR WITH BROADCASTING SUBSYSTEM!! Not sure if it is related, but there's another problem happening where obelisk-obworker exits when I run it after starting obelisk-obbalancer: DEBUG [worker]: Connecting: tcp://localhost:9092
INFO [worker]: worker ready
terminate called after throwing an instance of 'boost::interprocess::interprocess_exception'
what(): No such file or directory
Aborted (core dumped) At this point, obelisk-obbalancer crashes as well with this error: obelisk-obbalancer: balancer/balancer.cpp:130: std::string encode_uuid(const data_chunk&): Assertion `data.size() == 17' failed.
Aborted (core dumped) Obelisk doesn't seem very well documented at the moment. Does this client depend on Obelisk in some way? Note: I used makepkg to install libbitcoin-leveldb-git, obelisk-git, and sx-git from AUR. |
|
|
|
|
