Search content
Sort by
Showing 20 of 43 results by Blurb
Re: [ANN][EPC][Scrypt] Experiencecoin - The coin geared towards gamers- Release 3.0
Dude, go for a walk, chill a bit...
Lafu and Shotgun are both good people, with a sincere interest in crypto, they were just trying to help fix something that got broken. No need for an ego match here.
Without bothering to look at the src code, because I am lazy, and also busy, I would hazard a guess that whoever cloned up epc from doge didn't bother to change the network magic, and because of this, the doge wallets can happily chat with the epc wallets if they happen to connect with each other. The little chat only gets confused when they try exchanging blocks...then it all goes to hell.
Had the magic been made unique like it was intended, the wallets would disconnect instantly when discovering they are talking to the wallet for a different coin..with different network magic numbers..
It also isn't helping that you are giving out nodes with random port numbers stuck at the end, this will not work. That is the outbound port for the connection, you want a node address to point to the inbound port (the P2Port), that is the only port the other wallet is LISTENING on ...
Lafu and Shotgun are both good people, with a sincere interest in crypto, they were just trying to help fix something that got broken. No need for an ego match here.
Without bothering to look at the src code, because I am lazy, and also busy, I would hazard a guess that whoever cloned up epc from doge didn't bother to change the network magic, and because of this, the doge wallets can happily chat with the epc wallets if they happen to connect with each other. The little chat only gets confused when they try exchanging blocks...then it all goes to hell.
Had the magic been made unique like it was intended, the wallets would disconnect instantly when discovering they are talking to the wallet for a different coin..with different network magic numbers..
It also isn't helping that you are giving out nodes with random port numbers stuck at the end, this will not work. That is the outbound port for the connection, you want a node address to point to the inbound port (the P2Port), that is the only port the other wallet is LISTENING on ...
[I'm really angry at Cryptopia ...]
Don't throw it all on the exchange, many of the coins you mentioned are really broken. Kangeroo Bits is hopelessly broken, I actually was looking at fixing it at one point, it is broken beyond any hope of repair. Fire Rooster dropped dead, there are no nodes anywhere on the planet, you can't really blame the exchange for that.
Lemon is marked on topia's delisting info page as having a non-functional wallet or chain, so it still has a chance, if someone is willing to work on the issue..
Don't throw it all on the exchange, many of the coins you mentioned are really broken. Kangeroo Bits is hopelessly broken, I actually was looking at fixing it at one point, it is broken beyond any hope of repair. Fire Rooster dropped dead, there are no nodes anywhere on the planet, you can't really blame the exchange for that.
Lemon is marked on topia's delisting info page as having a non-functional wallet or chain, so it still has a chance, if someone is willing to work on the issue..
Re: [$XVG] VERGE [POW][MultiAlgo][BLACKHOLE][Entire Line of TOR/i2P Resources]
Hardfork was poorly executed and the latest version of the wallet requires specific libraries (libseccomp, libcap) that are only available on Linux.
You need to give exchanges and pool operators a clear schedule and ample amount of time (months) not days or weeks to prepare for a hardfork.
I hope someone can help me figure out how to build the new wallet on platforms other than Linux that do not support seccomp and libcap.
You need to give exchanges and pool operators a clear schedule and ample amount of time (months) not days or weeks to prepare for a hardfork.
I hope someone can help me figure out how to build the new wallet on platforms other than Linux that do not support seccomp and libcap.
im the same was setting up a pool and and getting the same errors
libseccomp, libcap not found etc
... Yes 2 libraries were needed, just install them ...
Thanks for listening.
WHY? Both libraries deal with programs running with superuser privelages,
why the hell are they needed for a user app?
Are the Linux folks really running wallets as root?
Re: ( [ANN] ) (PUNZ) - Making Crypto Great Again - Zerocoin Being Implemented
Yeah. a roadmap would be nice, or at least an outline of where we are going. And you will need a block explorer to be on most exchanges, they want some place for users to be able to figure out where their deposits went.
Also, something that doesn't cost much except a little time is some advertising, hardly anyone has even heard of this coin, which is too bad, it has nice staking and pow parameters, it should have more interest, but I don't think anyone even knows it exists.
Now sure why you want to do a swap, unless it is to go with zerocoin transaction format, fixing the wallet timing glitch would be nice tho, it is a pain that it drops so many mined blocks. What is ti with masternodes? Everyone wants masternodes, they are just glorified coin mixers, with zerocoin they would do nothing usefull anyhow..
Mostly tho, talk to us, trolls like to be talked to, lullabys mostly..
Also, something that doesn't cost much except a little time is some advertising, hardly anyone has even heard of this coin, which is too bad, it has nice staking and pow parameters, it should have more interest, but I don't think anyone even knows it exists.
Now sure why you want to do a swap, unless it is to go with zerocoin transaction format, fixing the wallet timing glitch would be nice tho, it is a pain that it drops so many mined blocks. What is ti with masternodes? Everyone wants masternodes, they are just glorified coin mixers, with zerocoin they would do nothing usefull anyhow..
Mostly tho, talk to us, trolls like to be talked to, lullabys mostly..
Also, in case no one noticed...
200000-299999 50 K Blocks
300000-699999 25 K Blocks
700000-724999 12.5 K Blocks
725000-749999 6.25 K Blocks
750000-779332 25 K Blocks
779333-789554 12.5 K Blocks
789555-822221 50 K Blocks << we were here
822222-833332 12.5 K Blocks <<--- We are now here
833333-888887 100 K Blocks
888888-900000 12.5 K Blocks
200000-299999 50 K Blocks
300000-699999 25 K Blocks
700000-724999 12.5 K Blocks
725000-749999 6.25 K Blocks
750000-779332 25 K Blocks
779333-789554 12.5 K Blocks
789555-822221 50 K Blocks << we were here
822222-833332 12.5 K Blocks <<--- We are now here
833333-888887 100 K Blocks
888888-900000 12.5 K Blocks
Anyone know what is up with Cryptopia?
"SC / BTC market is closing
Due to ongoing transaction issuesSiaCoin(SC) has been scheduled for delist, please close all open orders and withdraw your coins before 24/09/2017"
"SC / BTC market is closing
Due to ongoing transaction issuesSiaCoin(SC) has been scheduled for delist, please close all open orders and withdraw your coins before 24/09/2017"
[but i have a bad feeling the chain may have been forked.
so everony please compare to blockcrawler an post result pls.]
My local wallet matches exactly, with 4 connected notes, diff is low , but the chain is still running late from before...
--
The A2 will happily beat the hell out of a pool if you forget the stratum+ , don't do that lol
I have also found MRR masks certain error conditions sometimes, I suppose it is because it is taking the stratum info apart and putting it back together again, so some things that should be 'wrong' get fixed up, and nobody realizes the data is gibberish except the poor pool...
Chuckle that made my day on the explorer:
Connections:
15 Flappers
so everony please compare to blockcrawler an post result pls.]
My local wallet matches exactly, with 4 connected notes, diff is low , but the chain is still running late from before...
--
The A2 will happily beat the hell out of a pool if you forget the stratum+ , don't do that lol
I have also found MRR masks certain error conditions sometimes, I suppose it is because it is taking the stratum info apart and putting it back together again, so some things that should be 'wrong' get fixed up, and nobody realizes the data is gibberish except the poor pool...
Chuckle that made my day on the explorer:
Connections:
15 Flappers
[not sure, why, but we got one miner that is practically an overkill to the network hasrate].
Oops...
Because I was not paying attention for a few days and 2 other coins on the miner failed over, should have been only hitting it with around 15-20 at most, I will let the diff go back down, sorry folks.
[this reduces the pools to one.]
From a practical point however, when someone can solomine at a higher hashrate than all the pools combined, the coin is very vulnerable to being manipulated, flappy really does need a bit more hashrate, the only thing that prevents anyone from messing with it at the moment is that it isn't tradable for anything, . That will change when it gets listed on an exchange...
You do realize that if you implement merge mining, the difficulty of flappy will most likely be driven up to the difficulty of the child coin....
Long ago, myriad did a pool with merge mining of multiple coins, they handled the multiple wallet address issue by having the miners sign the aux addresses using their primary wallet, and then submitting the signed text to the pool, which then saved those addresses and associated them with the primary mining address, this allowed half a dozen aux coins to be included without making a gigantic mess out of the miner username field...
Oops...
Because I was not paying attention for a few days and 2 other coins on the miner failed over, should have been only hitting it with around 15-20 at most, I will let the diff go back down, sorry folks.
[this reduces the pools to one.]
From a practical point however, when someone can solomine at a higher hashrate than all the pools combined, the coin is very vulnerable to being manipulated, flappy really does need a bit more hashrate, the only thing that prevents anyone from messing with it at the moment is that it isn't tradable for anything, . That will change when it gets listed on an exchange...
You do realize that if you implement merge mining, the difficulty of flappy will most likely be driven up to the difficulty of the child coin....
Long ago, myriad did a pool with merge mining of multiple coins, they handled the multiple wallet address issue by having the miners sign the aux addresses using their primary wallet, and then submitting the signed text to the pool, which then saved those addresses and associated them with the primary mining address, this allowed half a dozen aux coins to be included without making a gigantic mess out of the miner username field...
Are you scrapping the idea of a 10:1 coin swap or so?
Because, you don't want to list on Cryptopia if you are going to swap the chain, they will make you pay for a new coin if you do that, so you should do that first...
Because, you don't want to list on Cryptopia if you are going to swap the chain, they will make you pay for a new coin if you do that, so you should do that first...