Pages:
Author

Topic: [ANN] [BLTZ] [IPO Hybrid] BlitzCoin | proof of concept coin | pure speculative - page 44. (Read 200984 times)

full member
Activity: 238
Merit: 100

Sorry for the noob question, but is there anything the dev could have done to avoid this kind of problems ? I see a lot of people blaming the dev but I always assumed that forks are like taxes, part of life xD.

no, nothing I could do. he was pressuring  me to relaunch the coin that have more than 6Gh/s
all other forked pools adopted in first hour, but he maintained fork for hours.

I think I'm sure the dev of this coin is a 13-14 yo kid without any idea how bitcoin/nodes/peers etc. work.

Of course he was able to do multiple things to let the coin NOT fork at launch, look at all the other coinlaunches without problems.
The dev is a total retard, that alone makes the coin absolutely worthless.

You cannot simply shut down a pool with 800mh/s and "resync" to an other fork assuming this is the correct one. A pool is no "windows box" which you reboot every 5 hours and shit on the users and its hashrate, you try to give them a decent service not a "f*ck you all, I'll delete everyone coins and simply jump on the other fork".

It was not just me who said you should relaunch your trash-coin, it was several users, of course NOT the users on one of the other forks.

Now, a day after the launch you STILL haven't got your coin under control moron.



Care to explain more about what could have been done ?.

relaunch will also delete the coins of your miners or not ? keeping the pool running in the wrong fork is even worse, that decision caused a lot of wasted electricity and the coins are lost anyways.

pool op abused other people resources by keeping it mine at his pool that was forked for hours. all other pools adopted to right fork in first hour.
coin relaunch was only solution, but network was 6Gh/s and relaunch was not an option.

abusing other people resources is serious issue. it shows how easy a pool op can abuse all gpu power in private purposes.
pool op can play with other people money and resources, and it can do what he want. because of that all users need to find a reliable pool that will not decide one day he want to use their resources for hours for other purposes..

as well, ocminer didn't provide IP for addnode, like most of the pools to be honest. adding a pool IP as addnode is reducing orphans on the pool, and making forks is almost impossible.

Abusing GPU Power ?! For what ?? For YOUR f*cking retard coin you mega-moron, do you even think before you write ? The Pool was for YOUR coin, it was not for MY pleasure or for makeing me happy, it was dedicated to support YOUR idea and the miners on the pool were YOUR miners !

That makes it even clearer that you're a young boy without any understanding of how things work out.

A pool never "provides" an IP, but if you need it, I explain it to you:

Open a DOS Box, thats "Start-Execute cmd"
Then enter this: "ping retardcoin.moronhead.com"

The resulting IP you get is the IP of the pool. So even if you urgently NEED the IP but pool does not provide it, as you say, you can simply ping the host and you GOT the ip.

And you again did not understand .. there was no clear "right fork" in the first hour... read in the history of this thread..

You're the most - wait - the MOST retarded dev of a coin I ever, ever, ever read about.. unbelievable.. Stole a coin, launch bullshit and blames it's own supporters .. lol

you kept miners on a fork for hours not me.

ocminer 1 : 0 BlitzCoinDev

Looks like the arguments from the dev run out.
member
Activity: 98
Merit: 10
any news on Android wallet ?
newbie
Activity: 15
Merit: 0
Any Mac OS X Wallets available?
hero member
Activity: 676
Merit: 500
full member
Activity: 154
Merit: 100
Dev posts are killing my profits....

There isn't any profits to be made.  Mintpal already knows about the shitstorm.  You guys think this is going to be like BC you're sadly mistaken.

It'll be on a few fringe exchanges, get dumped, and forgotten.  No self-respecting exchange is going to host this daemon.



We will see..., I will save this quote for later in case the price rise or tank, until now the price is not as bad as someone would expect after a failed launch. And greed is a very good motivator in the crypto world.
full member
Activity: 238
Merit: 100
Dev posts are killing my profits....

There isn't any profits to be made.  Mintpal already knows about the shitstorm.  You guys think this is going to be like BC you're sadly mistaken.

It'll be on a few fringe exchanges, get dumped, and forgotten.  No self-respecting exchange is going to host this daemon.

legendary
Activity: 2688
Merit: 1240
Dev posts are killing my profits.... ok time to sleep good night.

you better sell as long as you can
newbie
Activity: 42
Merit: 0

Sorry for the noob question, but is there anything the dev could have done to avoid this kind of problems ? I see a lot of people blaming the dev but I always assumed that forks are like taxes, part of life xD.

no, nothing I could do. he was pressuring  me to relaunch the coin that have more than 6Gh/s
all other forked pools adopted in first hour, but he maintained fork for hours.

I think I'm sure the dev of this coin is a 13-14 yo kid without any idea how bitcoin/nodes/peers etc. work.

Of course he was able to do multiple things to let the coin NOT fork at launch, look at all the other coinlaunches without problems.
The dev is a total retard, that alone makes the coin absolutely worthless.

You cannot simply shut down a pool with 800mh/s and "resync" to an other fork assuming this is the correct one. A pool is no "windows box" which you reboot every 5 hours and shit on the users and its hashrate, you try to give them a decent service not a "f*ck you all, I'll delete everyone coins and simply jump on the other fork".

It was not just me who said you should relaunch your trash-coin, it was several users, of course NOT the users on one of the other forks.

Now, a day after the launch you STILL haven't got your coin under control moron.



Care to explain more about what could have been done ?.

relaunch will also delete the coins of your miners or not ? keeping the pool running in the wrong fork is even worse, that decision caused a lot of wasted electricity and the coins are lost anyways.

pool op abused other people resources by keeping it mine at his pool that was forked for hours. all other pools adopted to right fork in first hour.
coin relaunch was only solution, but network was 6Gh/s and relaunch was not an option.

abusing other people resources is serious issue. it shows how easy a pool op can abuse all gpu power in private purposes.
pool op can play with other people money and resources, and it can do what he want. because of that all users need to find a reliable pool that will not decide one day he want to use their resources for hours for other purposes..

as well, ocminer didn't provide IP for addnode, like most of the pools to be honest. adding a pool IP as addnode is reducing orphans on the pool, and making forks is almost impossible.

Abusing GPU Power ?! For what ?? For YOUR f*cking retard coin you mega-moron, do you even think before you write ? The Pool was for YOUR coin, it was not for MY pleasure or for makeing me happy, it was dedicated to support YOUR idea and the miners on the pool were YOUR miners !

That makes it even clearer that you're a young boy without any understanding of how things work out.

A pool never "provides" an IP, but if you need it, I explain it to you:

Open a DOS Box, thats "Start-Execute cmd"
Then enter this: "ping retardcoin.moronhead.com"

The resulting IP you get is the IP of the pool. So even if you urgently NEED the IP but pool does not provide it, as you say, you can simply ping the host and you GOT the ip.

And you again did not understand .. there was no clear "right fork" in the first hour... read in the history of this thread..

You're the most - wait - the MOST retarded dev of a coin I ever, ever, ever read about.. unbelievable.. Stole a coin, launch bullshit and blames it's own supporters .. lol

you kept miners on a fork for hours not me.
full member
Activity: 154
Merit: 100
Dev posts are killing my profits.... ok time to sleep good night.
legendary
Activity: 2688
Merit: 1240

Sorry for the noob question, but is there anything the dev could have done to avoid this kind of problems ? I see a lot of people blaming the dev but I always assumed that forks are like taxes, part of life xD.

no, nothing I could do. he was pressuring  me to relaunch the coin that have more than 6Gh/s
all other forked pools adopted in first hour, but he maintained fork for hours.

I think I'm sure the dev of this coin is a 13-14 yo kid without any idea how bitcoin/nodes/peers etc. work.

Of course he was able to do multiple things to let the coin NOT fork at launch, look at all the other coinlaunches without problems.
The dev is a total retard, that alone makes the coin absolutely worthless.

You cannot simply shut down a pool with 800mh/s and "resync" to an other fork assuming this is the correct one. A pool is no "windows box" which you reboot every 5 hours and shit on the users and its hashrate, you try to give them a decent service not a "f*ck you all, I'll delete everyone coins and simply jump on the other fork".

It was not just me who said you should relaunch your trash-coin, it was several users, of course NOT the users on one of the other forks.

Now, a day after the launch you STILL haven't got your coin under control moron.



Care to explain more about what could have been done ?.

relaunch will also delete the coins of your miners or not ? keeping the pool running in the wrong fork is even worse, that decision caused a lot of wasted electricity and the coins are lost anyways.

pool op abused other people resources by keeping it mine at his pool that was forked for hours. all other pools adopted to right fork in first hour.
coin relaunch was only solution, but network was 6Gh/s and relaunch was not an option.

abusing other people resources is serious issue. it shows how easy a pool op can abuse all gpu power in private purposes.
pool op can play with other people money and resources, and it can do what he want. because of that all users need to find a reliable pool that will not decide one day he want to use their resources for hours for other purposes..

as well, ocminer didn't provide IP for addnode, like most of the pools to be honest. adding a pool IP as addnode is reducing orphans on the pool, and making forks is almost impossible.


You know, if you didn't present yourself as an amateur that didn't even show up for your second launch, dedicatedpool would of been on board.  You scared away all the good pools, then the scampools hopped on over the hype.  

Nice job creating another shitcoin.



+11111

full member
Activity: 238
Merit: 100

Sorry for the noob question, but is there anything the dev could have done to avoid this kind of problems ? I see a lot of people blaming the dev but I always assumed that forks are like taxes, part of life xD.

no, nothing I could do. he was pressuring  me to relaunch the coin that have more than 6Gh/s
all other forked pools adopted in first hour, but he maintained fork for hours.

I think I'm sure the dev of this coin is a 13-14 yo kid without any idea how bitcoin/nodes/peers etc. work.

Of course he was able to do multiple things to let the coin NOT fork at launch, look at all the other coinlaunches without problems.
The dev is a total retard, that alone makes the coin absolutely worthless.

You cannot simply shut down a pool with 800mh/s and "resync" to an other fork assuming this is the correct one. A pool is no "windows box" which you reboot every 5 hours and shit on the users and its hashrate, you try to give them a decent service not a "f*ck you all, I'll delete everyone coins and simply jump on the other fork".

It was not just me who said you should relaunch your trash-coin, it was several users, of course NOT the users on one of the other forks.

Now, a day after the launch you STILL haven't got your coin under control moron.



Care to explain more about what could have been done ?.

relaunch will also delete the coins of your miners or not ? keeping the pool running in the wrong fork is even worse, that decision caused a lot of wasted electricity and the coins are lost anyways.

pool op abused other people resources by keeping it mine at his pool that was forked for hours. all other pools adopted to right fork in first hour.
coin relaunch was only solution, but network was 6Gh/s and relaunch was not an option.

abusing other people resources is serious issue. it shows how easy a pool op can abuse all gpu power in private purposes.
pool op can play with other people money and resources, and it can do what he want. because of that all users need to find a reliable pool that will not decide one day he want to use their resources for hours for other purposes..

as well, ocminer didn't provide IP for addnode, like most of the pools to be honest. adding a pool IP as addnode is reducing orphans on the pool, and making forks is almost impossible.


You know, if you didn't present yourself as an amateur that didn't even show up for your second launch, dedicatedpool would of been on board.  You scared away all the good pools, then the scampools hopped on over the hype.  

Nice job creating another shitcoin.

legendary
Activity: 2688
Merit: 1240

Sorry for the noob question, but is there anything the dev could have done to avoid this kind of problems ? I see a lot of people blaming the dev but I always assumed that forks are like taxes, part of life xD.

no, nothing I could do. he was pressuring  me to relaunch the coin that have more than 6Gh/s
all other forked pools adopted in first hour, but he maintained fork for hours.

I think I'm sure the dev of this coin is a 13-14 yo kid without any idea how bitcoin/nodes/peers etc. work.

Of course he was able to do multiple things to let the coin NOT fork at launch, look at all the other coinlaunches without problems.
The dev is a total retard, that alone makes the coin absolutely worthless.

You cannot simply shut down a pool with 800mh/s and "resync" to an other fork assuming this is the correct one. A pool is no "windows box" which you reboot every 5 hours and shit on the users and its hashrate, you try to give them a decent service not a "f*ck you all, I'll delete everyone coins and simply jump on the other fork".

It was not just me who said you should relaunch your trash-coin, it was several users, of course NOT the users on one of the other forks.

Now, a day after the launch you STILL haven't got your coin under control moron.



Care to explain more about what could have been done ?.

relaunch will also delete the coins of your miners or not ? keeping the pool running in the wrong fork is even worse, that decision caused a lot of wasted electricity and the coins are lost anyways.

pool op abused other people resources by keeping it mine at his pool that was forked for hours. all other pools adopted to right fork in first hour.
coin relaunch was only solution, but network was 6Gh/s and relaunch was not an option.

abusing other people resources is serious issue. it shows how easy a pool op can abuse all gpu power in private purposes.
pool op can play with other people money and resources, and it can do what he want. because of that all users need to find a reliable pool that will not decide one day he want to use their resources for hours for other purposes..

as well, ocminer didn't provide IP for addnode, like most of the pools to be honest. adding a pool IP as addnode is reducing orphans on the pool, and making forks is almost impossible.

Abusing GPU Power ?! For what ?? For YOUR f*cking retard coin you mega-moron, do you even think before you write ? The Pool was for YOUR coin, it was not for MY pleasure or for makeing me happy, it was dedicated to support YOUR idea and the miners on the pool were YOUR miners !

That makes it even clearer that you're a young boy without any understanding of how things work out.

A pool never "provides" an IP, but if you need it, I explain it to you:

Open a DOS Box, thats "Start-Execute cmd"
Then enter this: "ping retardcoin.moronhead.com"

The resulting IP you get is the IP of the pool. So even if you urgently NEED the IP but pool does not provide it, as you say, you can simply ping the host and you GOT the ip.

And you again did not understand .. there was no clear "right fork" in the first hour... read in the history of this thread..

You're the most - wait - the MOST retarded dev of a coin I ever, ever, ever read about.. unbelievable.. Stole a coin, launch bullshit and blames it's own supporters .. lol
newbie
Activity: 42
Merit: 0

Sorry for the noob question, but is there anything the dev could have done to avoid this kind of problems ? I see a lot of people blaming the dev but I always assumed that forks are like taxes, part of life xD.

no, nothing I could do. he was pressuring  me to relaunch the coin that have more than 6Gh/s
all other forked pools adopted in first hour, but he maintained fork for hours.

I think I'm sure the dev of this coin is a 13-14 yo kid without any idea how bitcoin/nodes/peers etc. work.

Of course he was able to do multiple things to let the coin NOT fork at launch, look at all the other coinlaunches without problems.
The dev is a total retard, that alone makes the coin absolutely worthless.

You cannot simply shut down a pool with 800mh/s and "resync" to an other fork assuming this is the correct one. A pool is no "windows box" which you reboot every 5 hours and shit on the users and its hashrate, you try to give them a decent service not a "f*ck you all, I'll delete everyone coins and simply jump on the other fork".

It was not just me who said you should relaunch your trash-coin, it was several users, of course NOT the users on one of the other forks.

Now, a day after the launch you STILL haven't got your coin under control moron.



Care to explain more about what could have been done ?.

relaunch will also delete the coins of your miners or not ? keeping the pool running in the wrong fork is even worse, that decision caused a lot of wasted electricity and the coins are lost anyways.

pool op abused other people resources by keeping it mine at his pool that was forked for hours. all other pools adopted to right fork in first hour.
coin relaunch was only solution, but network was 6Gh/s and relaunch was not an option.

abusing other people resources is serious issue. it shows how easy a pool op can abuse all gpu power in private purposes.
pool op can play with other people money and resources, and it can do what he want. because of that all users need to find a reliable pool that will not decide one day he want to use their resources for hours for other purposes..

as well, ocminer didn't provide IP for addnode, like most of the pools to be honest. adding a pool IP as addnode is reducing orphans on the pool, and making forks is almost impossible.
full member
Activity: 154
Merit: 100

There are tons of possibilities, here are three:

1. Proper seednodes
Use dnsseed.yourcoinname.org to resolve to (at least) 6 or more nodes running the "correct" chain of the coin. The "wallets" then connect to this nodes and use them as the preffered blocksource.

2. Higher diff right from the start instead of incredible 0.00000123 diff

3. Post "addnode=" right from the start, not the pool nodes as they will sync up later on, YOUR nodes.


I believe the "dev" doesn't had enough pocket money to afford some VPS's for the seed nodes, so he fully relied on the pools, which then were all on separate forks. Yes, a relaunch for sure deletes or resets the wallets of the users, since there were multiple forks this would be the fairest possibility. This way simply one pool was chosen to be on "the right" chain and thats it.

Note that there is no really "right" chain in a fork.. Here we had the problem that there were even 4-5 forks, all different chains. So who decides which is the right/wrong fork ?  

However, the coins idea is not bad even though the dev stole the idea from someone else and postponed the launch 2 times which should make my alarm bells ring like it did for dedicatedpool already, they were right, I was wrong - shit happens. It just pisses me off that retard-dev takes absolutely no repsonsibility for his shit and instead blames others for his incompetence, his failure(s).

Thanks for the explanation!
legendary
Activity: 2688
Merit: 1240

Sorry for the noob question, but is there anything the dev could have done to avoid this kind of problems ? I see a lot of people blaming the dev but I always assumed that forks are like taxes, part of life xD.

no, nothing I could do. he was pressuring  me to relaunch the coin that have more than 6Gh/s
all other forked pools adopted in first hour, but he maintained fork for hours.

I think I'm sure the dev of this coin is a 13-14 yo kid without any idea how bitcoin/nodes/peers etc. work.

Of course he was able to do multiple things to let the coin NOT fork at launch, look at all the other coinlaunches without problems.
The dev is a total retard, that alone makes the coin absolutely worthless.

You cannot simply shut down a pool with 800mh/s and "resync" to an other fork assuming this is the correct one. A pool is no "windows box" which you reboot every 5 hours and shit on the users and its hashrate, you try to give them a decent service not a "f*ck you all, I'll delete everyone coins and simply jump on the other fork".

It was not just me who said you should relaunch your trash-coin, it was several users, of course NOT the users on one of the other forks.

Now, a day after the launch you STILL haven't got your coin under control moron.



Care to explain more about what could have been done ?.

relaunch will also delete the coins of your miners or not ? keeping the pool running in the wrong fork is even worse, that decision caused a lot of wasted electricity and the coins are lost anyways.

There are tons of possibilities, here are three:

1. Proper seednodes
Use dnsseed.yourcoinname.org to resolve to (at least) 6 or more nodes running the "correct" chain of the coin. The "wallets" then connect to this nodes and use them as the preffered blocksource.

2. Higher diff right from the start instead of incredible 0.00000123 diff

3. Post "addnode=" right from the start, not the pool nodes as they will sync up later on, YOUR nodes.


I believe the "dev" doesn't had enough pocket money to afford some VPS's for the seed nodes, so he fully relied on the pools, which then were all on separate forks. Yes, a relaunch for sure deletes or resets the wallets of the users, since there were multiple forks this would be the fairest possibility. This way simply one pool was chosen to be on "the right" chain and thats it.

Note that there is no really "right" chain in a fork.. Here we had the problem that there were even 4-5 forks, all different chains. So who decides which is the right/wrong fork ?  

However, the coins idea is not bad even though the dev stole the idea from someone else and postponed the launch 2 times which should make my alarm bells ring like it did for dedicatedpool already, they were right, I was wrong - shit happens. It just pisses me off that retard-dev takes absolutely no repsonsibility for his shit and instead blames others for his incompetence, his failure(s).
full member
Activity: 238
Merit: 100
The P2Pool source code connects to the current network. Just make sure that you guys are correctly synced. The only reason I switched was because invalid blocks were being submitted and not paying out. That pool was receiving payout when valid blocks were found however so it was unfair to the miners.

Hopefully this issue was resolved. I'll be keeping a close eye on the P2Pool network again.

Sorry for the inconvenience

Thanks Omar, I moved back to your node now.  I am watching it as well.... back down to 1/10th of what I should be getting. :-(

P2pool is terrible.  You just have to look at the orphan DOA rates of these pools to understand you're losing 20-30% of your hash rates :p

full member
Activity: 238
Merit: 100

Sorry for the noob question, but is there anything the dev could have done to avoid this kind of problems ? I see a lot of people blaming the dev but I always assumed that forks are like taxes, part of life xD.

no, nothing I could do. he was pressuring  me to relaunch the coin that have more than 6Gh/s
all other forked pools adopted in first hour, but he maintained fork for hours.

I think I'm sure the dev of this coin is a 13-14 yo kid without any idea how bitcoin/nodes/peers etc. work.

Of course he was able to do multiple things to let the coin NOT fork at launch, look at all the other coinlaunches without problems.

The dev is a total retard, that alone makes the coin absolutely worthless.

You cannot simply shut down a pool with 800mh/s and "resync" to an other fork assuming this is the correct one. A pool is no "windows box" which you reboot every 5 hours and shit on the users and its hashrate, you try to give them a decent service not a "f*ck you all, I'll delete everyone coins and simply jump on the other fork".

It was not just me who said you should relaunch your trash-coin, it was several users, of course NOT the users on one of the other forks.

Now, a day after the launch you STILL haven't got your coin under control moron.






sr. member
Activity: 1313
Merit: 302
The P2Pool source code connects to the current network. Just make sure that you guys are correctly synced. The only reason I switched was because invalid blocks were being submitted and not paying out. That pool was receiving payout when valid blocks were found however so it was unfair to the miners.

Hopefully this issue was resolved. I'll be keeping a close eye on the P2Pool network again.

Sorry for the inconvenience

Thanks Omar, I moved back to your node now.  I am watching it as well.... back down to 1/10th of what I should be getting. :-(
sr. member
Activity: 392
Merit: 250
The P2Pool source code connects to the current network. Just make sure that you guys are correctly synced. The only reason I switched was because invalid blocks were being submitted and not paying out. That pool was receiving payout when valid blocks were found however so it was unfair to the miners.

Hopefully this issue was resolved. I'll be keeping a close eye on the P2Pool network again.

Sorry for the inconvenience
full member
Activity: 154
Merit: 100

Sorry for the noob question, but is there anything the dev could have done to avoid this kind of problems ? I see a lot of people blaming the dev but I always assumed that forks are like taxes, part of life xD.

no, nothing I could do. he was pressuring  me to relaunch the coin that have more than 6Gh/s
all other forked pools adopted in first hour, but he maintained fork for hours.

I think I'm sure the dev of this coin is a 13-14 yo kid without any idea how bitcoin/nodes/peers etc. work.

Of course he was able to do multiple things to let the coin NOT fork at launch, look at all the other coinlaunches without problems.
The dev is a total retard, that alone makes the coin absolutely worthless.

You cannot simply shut down a pool with 800mh/s and "resync" to an other fork assuming this is the correct one. A pool is no "windows box" which you reboot every 5 hours and shit on the users and its hashrate, you try to give them a decent service not a "f*ck you all, I'll delete everyone coins and simply jump on the other fork".

It was not just me who said you should relaunch your trash-coin, it was several users, of course NOT the users on one of the other forks.

Now, a day after the launch you STILL haven't got your coin under control moron.



Care to explain more about what could have been done ?.

relaunch will also delete the coins of your miners or not ? keeping the pool running in the wrong fork is even worse, that decision caused a lot of wasted electricity and the coins are lost anyways.
Pages:
Jump to: