its not my style to call scam...but im doing it
so someone ad a shit load of coin on coinedup...and they where worth 0.001btc so he revamp asr so it gain value and he made a unstable wallet so nobody can cash out...
so now he is dumping freely all the coins that he already ad on coined up
Watch when you make accusations mate , you are driving out the community and proves you are not one of them! :S |
|
|
|
I lose more than half of the coin after update to the new folk. What?!
So I decide back to the old folk. And wish the best of you guys.
We have been screaming to folks to update to the new client for almost two+ weeks now. I am not sure what will happen with your coins on the old fork; good luck. We might be able to learn something from the Peercoin community. It takes much more time for such a big step. The GLX coins I recently bought from cryptsy.com are gone. You guys even haven't given the biggest exchange cryptsy.com enough time to response. Now, we still see many pool/exchange running on old folk. That means the GLX community haven't synchronized within two weeks! Thanks for your guys, we have double fun from two GLX networks now. It is true that the fork happened a lot sooner than we wanted to; you can point the figures at the dev. team and myself for that. But everyone has made extraordinary efforts to iron the issues out since then. How many members of other alt-coins produced videos and scripts to deal with getting people on the new fork? And I am not talking about advertisement videos but actual assistance and support to folks affected? I should not talk to a community contributor in that way. Plz accept my apology.  A community contributor should not be treated and talked to that way and made fun of , if you really wanted to put blames please do so to the original dev , who made a coin and abandoned it , you should be grateful , if not for this team , GLX would be long gone and dead and all your coins proved worthless and I believe there's an apology for the entire community who's putting their time and effort to keep GLX what it is and expect nothing in return , unlike devs who premine and run away with it , here it's about LOVE for what we LOVE to do mate and what we expect in return is appreciation and a little bit of respect for what we do. Please keep that in mind when throwing around blames. Regards, Soopy Community Developer |
|
|
|
|
listen=1
daemon=1
server=1
rpcuser=username
rpcpassword=password
rpcport=15332
port=14333
rpcconnect=127.0.0.1
addnode=coin-base.info:22477
addnode=188.187.61.58:14333
addnode=85.25.197.186:22477
addnode=94.153.88.241:14333
addnode=92.124.127.124:14333
addnode=81.65.188.29:14333
addnode=118.209.90.143:14333
|
|
|
|
|

[
{
"addr" : "188.187.61.58:14333",
"services" : "00000003",
"lastsend" : 1395376444,
"lastrecv" : 1395376422,
"bytessent" : 231155,
"bytesrecv" : 285622,
"blocksrequested" : 4,
"conntime" : 1395344112,
"version" : 70002,
"subver" : "/Satoshi:0.9.0/",
"inbound" : false,
"startingheight" : 20067,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "85.25.197.186:22477",
"services" : "00000003",
"lastsend" : 1395376444,
"lastrecv" : 1395376446,
"bytessent" : 91454,
"bytesrecv" : 216951,
"blocksrequested" : 0,
"conntime" : 1395348549,
"version" : 70002,
"subver" : "/Satoshi:0.9.0/",
"inbound" : false,
"startingheight" : 20095,
"banscore" : 0
},
{
"addr" : "94.153.88.241:14333",
"services" : "00000003",
"lastsend" : 1395376444,
"lastrecv" : 1395376444,
"bytessent" : 178058,
"bytesrecv" : 214509,
"blocksrequested" : 0,
"conntime" : 1395348925,
"version" : 70002,
"subver" : "/Satoshi:0.9.0/",
"inbound" : false,
"startingheight" : 20097,
"banscore" : 0
},
{
"addr" : "92.124.127.124:14333",
"services" : "00000003",
"lastsend" : 1395376443,
"lastrecv" : 1395376430,
"bytessent" : 77301,
"bytesrecv" : 149232,
"blocksrequested" : 0,
"conntime" : 1395365416,
"version" : 70002,
"subver" : "/Satoshi:0.9.0/",
"inbound" : false,
"startingheight" : 20190,
"banscore" : 0
},
{
"addr" : "81.65.188.29:14333",
"services" : "00000003",
"lastsend" : 1395376415,
"lastrecv" : 1395376444,
"bytessent" : 30655,
"bytesrecv" : 148711,
"blocksrequested" : 0,
"conntime" : 1395367439,
"version" : 70002,
"subver" : "/Satoshi:0.9.0/",
"inbound" : false,
"startingheight" : 2553,
"banscore" : 0
},
{
"addr" : "118.209.90.143:14333",
"services" : "00000003",
"lastsend" : 1395376414,
"lastrecv" : 1395376443,
"bytessent" : 18615,
"bytesrecv" : 100817,
"blocksrequested" : 0,
"conntime" : 1395373485,
"version" : 70002,
"subver" : "/Satoshi:0.9.0/",
"inbound" : false,
"startingheight" : 20244,
"banscore" : 0
},
More nodes
|
|
|
|
I deleted the whole blockchain and the wallet started syncing with the coin-base and no-ip nodes, however it seems to be stuck at 17533...
It doesn't work that way my friend since we still need more clients on the new chain , because the old wallets are stuck on 17533. Regards, Soopy |
|
|
|
|
Since you are in the correct chain if you downloaded the wallet and also the the blockchain , you should be able to recieve payments from coin-base.info , try out a small amount to test with.
|
|
|
|
We need more nodes mates , setup a no-ip account and keep running your wallet for a few hours would help the community.  |
|
|
|
I've dowloaded and installed this chain. It looks like they may have forked at the right point, which is good. Bad news is that none of the peers my client is trying to connect to seem to be on this chain - the archive includes peers.dat so I was hoping I'd quickly be able to find such a peer. In addition, astrocoin.no-ip.biz does not appear to be up. So right now I'm "synced" to block 19882 (minted a little over an hour ago), but since I have no connections to suitable peers I'm effectively stuck in limbo. The chain will never extend. If someone connects to me now and syncs to the chain I have, then starts mining, they will create an additional fork! I'm not sure how people are withdrawing their coins from the pool, if there's no other peers on the right chain... maybe coin-base is on its own (effectively private) chain? We really need the IP of coin-base's client to properly join the network. I've updated the conf on the OP with the coin-base node as well as my node with the correct chain from Coin-base. Do let me know when you've synced my friend also we need more nodes on the new wallet , since it's a cat fight over here lol. Cheers! Soopy |
|
|
|
Well nearly there,
It is about 3.30 am here in Australia.
I started the client again after getting the new blockchain zip.
It was very fast in getting the block chain.
My ASR from the pool was in there as well.
I watched the debug window and the coinbase.info ASR pool info window.
I was watching the block chain numbers.
The client said block 20015
The pool info page said block 20016
When that block was done, the client showed it first by changing to 20016 and then the webpage changed to 20017 a few seconds later.
I tested a withdrawal from coinbase.info/astrocoin.
I got those ASR a few seconds later.
BUT.
The wallet still says Wallet (out of sync) and there are 0 hours behind.
So, for all intents and purposes, I seem to be on the correct blockchain.
I only had 1 node line in the astrocoin.conf file.
addnode=astrocoin.no-ip.biz
The only thing I do not understand is why the (out of sync) message remains.
Perhaps it needs more than one node for that to be gone.
Can anyone enlighten us there?
Awesome to hear that you are on the right chain , the out of sync message is due to the fact that we need more nodes on the correct chain and also the network is still seem to solving the current block! |
|
|
|
Should KGW change the difficulty at the fork point immediately or can it take several blocks before it starts the per-block adjustments? Went past the fork point about 10 hours ago, but difficulty hasn't changed...
15-Mar-2014 07:33:17 height: 17517 difficulty: 11.44455344 tx: 2
15-Mar-2014 20:36:48 height: 17518 difficulty: 11.44455344 tx: 3
16-Mar-2014 09:06:40 height: 17519 difficulty: 11.44455344 tx: 2
16-Mar-2014 16:27:27 height: 17520 difficulty: 11.44455344 tx: 10 <-- fork point
17-Mar-2014 00:26:08 height: 17521 difficulty: 11.44455344 tx: 2 <-- first use of KGW?
17-Mar-2014 00:51:50 height: 17522 difficulty: 11.44455344 tx: 1
18-Mar-2014 16:52:33 height: 17523 difficulty: 11.44455344 tx: 5
18-Mar-2014 18:05:05 height: 17524 difficulty: 11.44455344 tx: 1
18-Mar-2014 19:08:55 height: 17525 difficulty: 11.44455344 tx: 1
18-Mar-2014 21:33:20 height: 17526 difficulty: 11.44455344 tx: 2
18-Mar-2014 21:34:57 height: 17527 difficulty: 11.44455344 tx: 1
18-Mar-2014 22:14:02 height: 17528 difficulty: 11.44455344 tx: 1
18-Mar-2014 22:49:12 height: 17529 difficulty: 11.44455344 tx: 1
KGW Kicks in on the exact forking point and starts to first use of KGW on the next , it's quite simultaneous. |
|
|
|
Wallet Synced! 21:28:25  { "version" : 90000, "protocolversion" : 70002, "walletversion" : 60000, "balance" : 0.00000000, "blocks" : 20007, "timeoffset" : 0, "connections" : 2, "proxy" : "", "difficulty" : 2.43826461, "testnet" : false, "keypoololdest" : 1395331002, "keypoolsize" : 101, "paytxfee" : 0.00000000, "mininput" : 0.00001000, "errors" : "" } ------------------------------------------- { "blocks" : 20007, "currentblocksize" : 0, "currentblocktx" : 0, "difficulty" : 2.43826461, "errors" : "", "generate" : false, "genproclimit" : -1, "hashespersec" : 0, "networkhashps" : 75477327, "pooledtx" : 0, "testnet" : false } Peers -------  [ { "addr" : "85.25.197.186:22477", "services" : "00000003", "lastsend" : 1395331371, "lastrecv" : 1395331357, "bytessent" : 6530, "bytesrecv" : 142609, "blocksrequested" : 0, "conntime" : 1395331066, "version" : 70002, "subver" : "/Satoshi:0.9.0/", "inbound" : false, "startingheight" : 20007, "banscore" : 0, "syncnode" : true }, { "addr" : "221.210.16.66:9333", "services" : "00000001", "lastsend" : 1395331362, "lastrecv" : 1395331316, "bytessent" : 8247, "bytesrecv" : 250415, "blocksrequested" : 0, "conntime" : 1395331126, "version" : 70002, "subver" : "/Satoshi:0.8.5.1/", "inbound" : false, "startingheight" : 534040, "banscore" : 0 }, { "addr" : "85.199.4.228:9333", "services" : "00000003", "lastsend" : 1395331352, "lastrecv" : 1395331371, "bytessent" : 2695, "bytesrecv" : 109412, "blocksrequested" : 0, "conntime" : 1395331155, "version" : 70002, "subver" : "/Satoshi:0.8.6.1/", "inbound" : false, "startingheight" : 534930, "banscore" : 0 }, { "addr" : "119.246.18.143:9333", "services" : "00000001", "lastsend" : 1395331372, "lastrecv" : 1395331354, "bytessent" : 2262, "bytesrecv" : 96416, "blocksrequested" : 0, "conntime" : 1395331161, "version" : 70002, "subver" : "/Satoshi:0.8.5.1/", "inbound" : false, "startingheight" : 534930, "banscore" : 0 }, { "addr" : "109.26.29.213:9333", "services" : "00000003", "lastsend" : 1395331357, "lastrecv" : 1395331369, "bytessent" : 2329, "bytesrecv" : 104076, "blocksrequested" : 0, "conntime" : 1395331162, "version" : 70002, "subver" : "/Satoshi:0.8.6.1/", "inbound" : false, "startingheight" : 534930, "banscore" : 0 }, { "addr" : "96.248.105.24:9333", "services" : "00000003", "lastsend" : 1395331371, "lastrecv" : 1395331369, "bytessent" : 1437, "bytesrecv" : 96547, "blocksrequested" : 0, "conntime" : 1395331294, "version" : 70002, "subver" : "/Satoshi:0.8.6.2/", "inbound" : false, "startingheight" : 534932, "banscore" : 0 }, { "addr" : "70.70.44.232:9333", "services" : "00000003", "lastsend" : 1395331361, "lastrecv" : 1395331371, "bytessent" : 337, "bytesrecv" : 75724, "blocksrequested" : 0, "conntime" : 1395331323, "version" : 70002, "subver" : "/Satoshi:0.8.6.1/", "inbound" : false, "startingheight" : 534934, "banscore" : 0 } ] Setting up a node! Await! Reply from our very helpful friends at coin-base.info! Hello,
My current blocks are available under http://coin-base.info/astrocoin/asr-blockchain.tar.gz
In the astrocoin.conf listen=1 and maxconnections=50 and entered the port enabled. coin-base.info: 22477
But my test client gets no connection. Have a tip?
greetings!
ORtchi
Am 20.03.2014 06:05, schrieb Website Administration:
coin-base.info The ASR POOL Message,
Soopy Sent you a message
Senders Email: sherlockcoin@gmail.com
Subject: AstroCoin Blockchain Request
Personal message:
Hello Mate, Hope you are doing great, I'm the community Dev of Astrocoin and I see that you have synced to the network correctly and is the 1st and only pool minining Astrocoin and helping everyone. Some users are finding it hard syncing their wallets and I'm trying to setup a few nodes. Would be great if you can provide me with a zipped up and uploaded blockchain or please post here. https://bitcointalk.org/index.php?topic=516549 Thank you very much and very best regards. Soopy |
|
|
|
|
Why is it so hard for coin-base.info to cooperate and help get this coin on the track!
|
|
|
|
|
Hello All! Smiley
Sorry for the late replies , been having issues with my internet.
Will post updates in a few.
Regards,
~Soopy~
|
|
|
|
Hello All! Sorry for the late replies , been having issues with my internet. Will post updates in a few. Regards, ~Soopy~ |
|
|
|
... the best way to curb difficulty is using KGW and tweaking it for the best of BEE and as far as POS is more for the holders , what I suggest is first add KGW difficulty retarget formula tweaked for BEE and then later on when BEE goes BEEing we'd go ahead with POS
Also i did see some discussion that KGW has some security issues? aurora are worried about introducing it. CGA coin has removed KGW from their code to avoid exploits... Orbit has PoS already implemented, if you want to take a look at their code. Only the Orbit dev (TheRedMist) is MIA, we have recently only seen support from a hired dev Ghostlander. KGW has not been verified totally and is on theory and sandboxed operations and not tested on a real blockchain with 100 - 1000s of wallets and miners so yah , a network is secured by the number miners mining and the support of the end users thus it is what makes the network stronger to outside attacks , KGW is simply an algorithm to curb retarget issues and multipool attacks so even if exploited will not make any drastic impacts to the coin.POS implementation is not an issue , it's just that we need to get the priorities straighted out and discussed with the tops in the community such as Cryptohunter and John since they are the one's who know's what the community needs. PS: Orbitcoin became an entire mess sometime back. Regards, Soopy If the exploit is possible then I wound't be so sure about this. Looking at the thread BCX started , the exploit itself would lead to far more dangerous options for the attacker. True any exploit gives dangerous options for the attacker but then again on the same thread someone challenged BCX to exploit Mazacoin but then it's yet to be tested on a real world scenario. But I still doubt about the exploit and yet believe in the alogrithm, it's ultimatly the community's choice in embracing the same or not , thereby I'm not trying to push anything on to the community if they don't want it , just putting it all on the table , also the Kimoto Algorithm is widely used. And while disecting and studying the algorithm I have not been able to find flaws with it though found many on other features. ~Soopy~ If you think it is best Soopy we got with whatever plan you think best. If you take over as dev on Beecoin that would be great and you will have full control regarding the coin. I was just wondering? does Bee not already have KGW ? It seems to have a very strong diff adjust every block. If you think it is best for us to wait to have POS implemented then that is what we will do. I am very confident the network will grow rapidly once we decide on the coins plan and implement that, because we will start a very large marketing and givewaway campaign. Will the 2% 2% 1% block taxes be easy to code in? It would be great my friend if you can list out everything you and the community is looking to see implemented in a list here so everyone will know what they can expect. I'm going to start working on the taxes tonight and most probably release a new client update within a couple of hours. ~Soopy~ |
|
|
|
I'm having a lot of problems with clients on the older fork. There seems to be a fundamental bug in *coin code (not just GLX) where if there is a fork the clients on the "old" chain will repeatedly sent getblocks requests, asking for the same set of blocks, in an endless loop. It never stops. This consumes CPU and (in my case, more significantly) bandwidth.
I've had to resort to firewalling peers showing a height of 250k.
Yup something we've experienced before mate and see it happen over and over again , also suggested increasing the number of nodes with new wallets so the the new chain will take over. 51% attack literally. ~Soopy~ |
|
|
|
hey Soopy mac wallet available? Should be compiled in a few hours mate. |
|
|
|
Is there any update on the extra nodes?
Wallet still doesnt sync..says no block available
btw many thanks for all the effort soopy..
You are most welcome mate , I'm yet to recieve a copy of the blockchain from coin-base , thereafter I'm able to setup a few nodes for everyone to sync without much effort. ~Soopy~ |
|
|
|
Added Walletnotify! |
|
|
|
One astro just leaved the space dock - destination soopy  greetings Haha! Thank you very much mate , may you recieve evermore! Cheers! ~Soopy~ |
|
|
|
|
Show Posts
