I'm really interested what happens in 10 minutes.. or .. what happens in 15 minutes ^^
-Coin is a scam blatant copy of Panda source -Launch is scam (twice) -IPO is a scam Do you really have to ask?
|
|
|
COIN IS BEING RELAUNCHED IN 45 MINUTES - 1:30 AM EST - PROPER BLOCKS - DELETE ALL THE OLD STUFF
Why do we have to hear second hand news? He at least should update the original post with the most current information, especially being he took money upfront from the community and now has two failed launches. The whole situation reaks of a SCAM.
|
|
|
Be careful who you trade with folks, I would bet your money many are going to be passing off yesterdays fork launch coins as today's You have been warned.
|
|
|
Just another scam launch very few of the pools are up and the ones that are haven't found any blocks despite 10's of MH/s hash.
|
|
|
And it will auto-switch on GPUcoin when they become minable ? Yes, if you use it as a failover address. Use a vertminer configuration file or this string example: ./cgminer --scrypt -o stratum+tcp://GPUCOIN.POOL.COM:3333 -u Weblogin.Worker -p Worker password -o stratum+tcp://PANDA.POOL.COM:4444 -u Weblogin.Worker -p Worker password That will mine at the Panda pool until the GPUcoin pool comes online.
|
|
|
in vertminer .bat i need to put --scrypt/--nscrypt or nothing?
Just use the standard scrypt string: /cgminer --scrypt -o stratum+tcp://gpucoinpool.com:3361 -u Weblogin.Worker -p Worker password You may need to adjust the thread-concurrency to minimize invalid shares. More info here: https://bitcointalk.org/index.php?topic=416572.msg4519340#msg4519340
|
|
|
has a solo port been established?
RPC PORT = 6857
|
|
|
Love the idea of trading Alt coins for real goods. Hopefully we will see this catch on. I will be mining from the start. Good luck! ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
i've beein minig aur for a day at http://aur.pool.mineabit.com/, the pool just now came back alive, before this stratum was working but the site would not open in browser, but after about a full day of mining with a hashrate of 600 khash/s, i only got 0.03 aurora! is it normal because i expected about 0.2 or even 0.3 aur per day with my hash. only two transaction have been listet in my transaction's page, one of them which is unconfirmed still, is it possible that my payouts haven't come yet because of the long intervals between blocks? The diff and network hashrate are exploding. With a block reward of 25 coins, you can't expect to make very many coins per day with the hash you have. In fact with a diff of 2800 and your hashrate of 600 kh/s, you can only expect to make ~0.1 AUR per day. In addition, you only get paid when the pool finds a block. The pool stats page shows they haven't found a block in over 18 hours, which is why you haven't received any recent payouts. http://aur.pool.mineabit.com/index.php?page=statistics&action=poolPool Hash Rate 231.030 MH/s Pool Efficiency 99.86% Current Active Workers 215 Current Difficulty 2819.29806734 Est. Next Difficulty 658.80001571 (Change in 15 Blocks) Est. Avg. Time per Round (Network) 10 minutes 41 seconds Est. Avg. Time per Round (Pool) 14 hours 33 minutes 32 seconds Est. Shares this Round 11547845 (done: 242.32%) Next Network Block 3866 (Current: 3865) Last Block Found 3769 Time Since Last Block 18 hours 27 minutes 48 seconds
|
|
|
My personal tip: When I need to login / withdraw BTC, I usually use a virtual keyboard where you simply press the keys with your mouse. It's much safer as it doesn't record the keyboard
Word. In fact the password mgr called Password Safe also has a virtual keyboard you can pull up anytime. This is great software, and it is free. KeePass is another open-source alternative as well. BinaryClock from Dedicated Pools has a good tutorial YouTube video on this subject.- https://www.youtube.com/watch?v=ksTRQqDoWwE
|
|
|
STRONGLY RECOMMENDED
In addition to immediately clearing the console history after you unlock, observe best-practices and don't even directly type in the unlock command, at least not the password part. Pull it from a password mgr, or if for some (bad) reason you don't use one, type it out in chunks in notepad, intermixed with garbage characters, then copy and paste chunk by chunk. If your computer has keylogging malware you could get seriously fucked otherwise.
+1 Never use the keyboard directly to type sensitive passwords. When I have to type a password, I use the Windows 8.1 on-screen keyboard which keyloggers can't pick up.
|
|
|
Anyone have confirmed coins yet? If so, how long did they take?
For most coins, it's usually 120 block confirmations. Since Einstenium has a 60 second block target, that should take about 2 hours per block.
|
|
|
I've gotten 120 Einsteinium in the last two hours, with a 1,800 Kh/s. What are you guys getting?
Mine are still unconfirmed though.
That seems very low. At an average diff of 11, with 1800 KH/s on a coin with a 998 block reward you should be getting about ~135 coins an hour.
|
|
|
MintPal voting is open too! Registered and logged in users can cast 6 votes an hour for a coin, unregistered users can cast 3 votes: https://www.mintpal.com/voting
|
|
|
why are my 998 coins immature?
Read the transaction details: Generated coins must mature 120 blocks before they can be spent. When you generated this block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, its state will change to "not accepted" and it won't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours.
WTF.. that sucks! Why is that? Because it's just like when you mine in a pool, you have to wait until the newly mined coins are confirmed after 120 blocks before you can withdraw them.
|
|
|
why are my 998 coins immature?
Read the transaction details: Generated coins must mature 120 blocks before they can be spent. When you generated this block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, its state will change to "not accepted" and it won't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours.
|
|
|
|