|
I usually don't like posting my pool info right after another pool, but I figured I'd let you guys know that I have upped the block finder's bonus to 10POT. In case you needed it in big, bold letters:
Pot.CripToe.Com has increased the block finder bonus to 10POT.
Thanks,
Fuse
|
|
|
|
Going with the idea that the issue could be that users are using the incorrect wallet version, I have started to look into what it would take to get this straightened out. I have found the following post from the spots thread: If you are can compile your own client, you can edit main.cpp lines 2373 and 2474 to this: if(pfrom->nVersion != 60080)
badVersion = true; That will only allow peers on 60080 protocol to connect, getting rid of all other chains, but also limiting you only to people running the 60080 protocol version of Spots Essentially this blocks node connections if the protocol number doesn't match what you set it to. I've noticed in the Tagcoin code as well that the code in the version.h was changed to allow older versions "for now". I'm not sure why this would be allowed if the older versions are suspected of being the issue with the orphans. Shut them out and move on... period. At least eliminate that variable from the orphan equation. So I went through and forked the tagcoin code to another github repo, changed the code to only allow versions 1.0.4 and higher, and submitted a pull request. I know that Mark and the team have the say on this kind of stuff, but I'm taking the connections to my pool in my own hands. Pool ops, you are more than welcome to use this code if it doesn't get pulled into the main code. It can be found here: https://github.com/ny2cafuse/tagcoinWhile investigating this, I marked down some IPs that were using the wrong client version. They went back all the way to 1.0.2. So yeah, people are dopes and haven't updated. They are as follows: 162.217.76.228 162.217.76.228.3wave.net 86.15.162.44 cpc23-alde4-2-0-cust43.6-2.cable.virginm.net 91.143.109.221 221-109-143-91.grazkom.at 198.23.230.253 host.colocrossing.com 95.85.33.207 scrypt2.megamultipool.com24.55.2.13 82-149-230-110.static.aixit.com 82.149.230.110 cpe-24-55-2-13.austin.res.rr.com 96.236.44.79 pool-96-236-44-79.albyny.fios.verizon.net 162.217.76.228 162.217.76.228.3wave.net If those IPs or DNS host names look familiar, as in they are yours, update your damn client. Notice the one in red? That's the megamultipool mining pool. I have contacted the pool OPs there to update their wallet. If I came across as brash, I'm sorry, but this is getting old. -Fuse |
|
|
|
Great, VarDiff! Thanks, mate! One correction, though- it's currently 2% fees. I corrected the original post to proper percentage. -Fuse |
|
|
|
|
I have reopened mining on Tagmining.com. We'll see how this goes. After many updates and code changes, I'm pretty sure we'll be running solid. So:
Tagmining.com is mining again.
-Fuse
|
|
|
|
|
Mining has resumed on Tagmining.
I'm not announcing it in the main TAG thread yet, but if you'd like to start mining again, give it a shot. Vesper and I have looked at a lot of fixes and code changes over the last couple weeks, and I believe that things should run smooth now, even with orphans. However, only time will tell, and I'll never know unless I get things up and running again.
Let me know if you guys run into any issues.
-Fuse
|
|
|
|
Very nice!
Is this possible in Excel? I tried to use "get external data from web" but excel doesn't recognize .json data! Please shed some light on me...
I apologize because this is not related to google spreadsheet / reviving an old thread!
Thanks!
Hey, mate. No need for apologies, it's a good question. I think with Excel, you could use get external data from web and just use the actual page to fetch the data from. I think excel just looks at the webpage, breaks it into it's xpath data, and then uses that xpath data to import into the spreadsheet. I'd have to verify, but I think that would be the way to go. I'll test it at work and report back. -Fuse |
|
|
|
|
A bleacher seat from the original Yankee's stadium, signed by Bernie Williams.
~12MH in mining equipment.
A Silhouette Cameo for the wife.
All of our Xmas presents this past Xmas.
20 Silver Eagles.
Lots of little things here and there- groceries, household goods, etc...
All things I couldn't had done normally/without help from family without Bitcoin in my life.
Thanks, Bitcoin!
-Fuse
|
|
|
|
Looking forward to Fuse opening up the pool back up and working some kind of magic to mitigate the orphans.
^Yeah, what those guys said!  Pool will open back up soon. Vesper and I, mostly Vesper in his honestly infinite wisdom, have been tracking stuff down and looking at how things work. Hopefully, with his help, I can mitigate what was going on before. Maybe this weekend, but don't hold me to it. -Fuse |
|
|
|
How do i know if my Pool is up to date?
You verify the proper block height, and you check your potcoind via getinfo for the version information. If your current block height and your version matches the other pools and github, respectively, you're golden. POT.CripToe.Com was already updated, and rocking and rolling.-Fuse |
|
|
|
Just to confirm: POT.CripToe.Comis on the latest version... and rocking and rolling. -Fuse |
|
|
|
I think that what is happening is due to old versions of the client still in use, some back to 1.0.2. Using getpeerinfo you can check that for yourself. Not a lot I can do about it except remind people to use the latest version. so as far as I am concerned the code is stable, the chain is stable and I can move forward with developments to use TAG in earnest.
Hard fork update with code that puts a lock on the sync process unless the user is updated to the latest version. If I remember correctly, I'm pretty sure it's how Litecoin did it last year. Basically, "if version !=x then sync=false". And they get a big red update notice in the area that says "you need to update you wallet or else you're a dope". Force them to update, and let's eliminate this variable. -Fuse |
|
|
|
POT.CripToe.Com is now rewarding a 5POT block finder bonus.This is to replace the 0% fee promotion that was going on until yesterday. Come give us a try! We won't bite -Fuse
|
|
|
|
There's still orphans occuring, not as bad as before, but it's odd how some pools seem to get waves and others don't. We're trying to look into possibilities why.
I've got an idea of why some pools aren't getting hit as hard with orphans lol. Hey, China... how's the weather over there? -Fuse |
|
|
|
|
Any updates on the code investigation? I'm interested to see what's found out.
-Fuse
|
|
|
|
we really need a dev to check. i'll see if i can get hold of one
First couple rounds of beers/shots are on me. -Fuse im muslim i dont drink  , but everyone else can have my share  A halal feast is in order then. Baraka Allah. -Fuse |
|
|
|
we really need a dev to check. i'll see if i can get hold of one
First couple rounds of beers/shots are on me. -Fuse |
|
|
|
Ahmed, thanks for the link.
Fuse, is this not the exact thing I told you about in chat lastnight? That it's likely due to some inexperienced developer tweaking settings to make the coin more responsive, and trying to sell it off as a feature? I'm buying a lotto ticket tonight.. I'm like 10 for 10 this week.
Action item: Look into the TAG code.
I don't mind doing this sometime today or tomorrow, but I'm guessing someone else here will beat me to it.
no problem If this is in fact the issue with TAG, I will be a very happy camper, and I will go on record as saying I was completely wrong about my suspicions of a network hack/attack. Fingers crossed. -Fuse |
|
|
|
This may or may not matter to the developer from a business standpoint, as long as there's a few MH, transactions will still work for the "rewards" system.
Mark can do this with his farm... smart move. -Fuse |
|
|
|
Have you guys had a previously-confirmed block (or more than one) turn orphan hundreds or thousands of confirmations later? That's always fun.
oh we certainly have. maybe even further. fixing the pools when it happens is all too fun too I hear you on that one, Ahmed! I honestly think at this point that there will not be a fix found, because it isn't a problem with the coin. If it's a code issue, the coins this code were based off of would have had similar issues before, giving us a solid basis for what the problem is. Now if by some chance it is a code issue, this will be an ongoing issue for a very long time and will probably kill this coin's support for the rest of it's life. If that's the case, you scrap this code and relaunch the coin as a straight 1 to 1 clone of something proven, like LTC or hell even EAC, and you cut your loses before they bleed you dry. I'm 100% sure that the dedicated community would probably get behind it, as it would be a wise choice for a push forward for the long term goal and future of TAG. Yes people will complain, as they probably hold a ton of coins waiting to dump at a later time, but it's the smart move for this coin's future, and the future of it's use for the Tagbond platform. Now.... if you do this, or even scrap POS as another attempted fix, and you find out it's still happening, then there's network manipulation. At that point, you're screwed either way, and any pool outside the sphere of the manipulator's protection will continue to orphan as long as they decide to shut us down with orphans. With the amount of trade volume on btc38 compared to cryptsy, and the fact that for some reason Botpool hasn't been getting hit as hard with the orphans after the fixes, I'm thinking the asian markets have some kind of hand in the manipulation. There, I said it. I know I'm getting into conspiracy theory stuff here, but I truly believe this is the case. China is trading 2-3 times the amount of TAG that the rest of the world is trading, and it's straight into Yuan. At this point, you cut the loses for the community by relaunching the coin on solid POW coin code, and you smoke out the rats. -Fuse just out of curiosity this isnt the negative retarget? bug which orbitcoin experienced recently? if the coin was to be relaunched i personally would say stick with POS but go for a coin like hobonickles. that has a solid codebase and an active and quite innovative dev (he created the first ever multi wallet QT) and afaik it hasnt had any of these issues. Ahmed, where have you been all my life? OK... so how do we check if this is the issue, and is this negative retarget issue fixable? Also, why would this only effect certain pools, or is this a completely random occurrence? -Fuse |
|
|
|
Have you guys had a previously-confirmed block (or more than one) turn orphan hundreds or thousands of confirmations later? That's always fun.
oh we certainly have. maybe even further. fixing the pools when it happens is all too fun too I hear you on that one, Ahmed! I honestly think at this point that there will not be a fix found, because it isn't a problem with the coin. If it's a code issue, the coins this code were based off of would have had similar issues before, giving us a solid basis for what the problem is. Now if by some chance it is a code issue, this will be an ongoing issue for a very long time and will probably kill this coin's support for the rest of it's life. If that's the case, you scrap this code and relaunch the coin as a straight 1 to 1 clone of something proven, like LTC or hell even EAC, and you cut your loses before they bleed you dry. I'm 100% sure that the dedicated community would probably get behind it, as it would be a wise choice for a push forward for the long term goal and future of TAG. Yes people will complain, as they probably hold a ton of coins waiting to dump at a later time, but it's the smart move for this coin's future, and the future of it's use for the Tagbond platform. Now.... if you do this, or even scrap POS as another attempted fix, and you find out it's still happening, then there's network manipulation. At that point, you're screwed either way, and any pool outside the sphere of the manipulator's protection will continue to orphan as long as they decide to shut us down with orphans. With the amount of trade volume on btc38 compared to cryptsy, and the fact that for some reason Botpool hasn't been getting hit as hard with the orphans after the fixes, I'm thinking the asian markets have some kind of hand in the manipulation. There, I said it. I know I'm getting into conspiracy theory stuff here, but I truly believe this is the case. China is trading 2-3 times the amount of TAG that the rest of the world is trading, and it's straight into Yuan. At this point, you cut the loses for the community by relaunching the coin on solid POW coin code, and you smoke out the rats. -Fuse |
|
|
|
|
Show Posts
