Search content
Sort by
Showing 13 of 13 results by Tux2
Hey everyone, just an update.
First, the official pools and why they're not paying out: I have no clue why they aren't paying out. I've tried everything I know to get them to pay but they won't. We've also got a backlog of transactions in the system that just won't confirm, that's something that I need to work on as well. This is my first rodeo on creating a coin and everything was going smoothly for the first few days. It's going to take some time and research to figure these things out. So, in the mean time I'm going to pull down the official pools so I can have the time to figure this out.
Please be patient. I got thrown in to the deep end of this by a friend that pushed me to get this coin out there without a proper development time, testing, research, etc. I also want to thank everyone for throwing your hashing power at the coin, and the stress testers, seeing what it can handle. If this was a network attack then it definitely left a huge mark on the coin. I've never done a project like this, and I admit that it was slapped together way too quickly for even my liking. I'm hoping to have the time within the next week to untangle everything, figure out what went wrong, and get it released properly. Will I be able to save the current block chain? I have no idea. Will you lose all your coins? Who knows. All of this is currently in the air. If anyone has more experience than us and is willing to help us out we'd definitely be grateful.
If you guys have any questions feel free to ask. I'll answer to the best of my ability. Just so you know, I do have another job and this has already taken up a significant chunk of my free time trying to figure out the network issues, pool issues, etc., but I am dedicated to figuring these issues out and making this coin work. Definitely a huge learning curve in a language (C++) I don't use very often and never really learned that well.
Tux2
First, the official pools and why they're not paying out: I have no clue why they aren't paying out. I've tried everything I know to get them to pay but they won't. We've also got a backlog of transactions in the system that just won't confirm, that's something that I need to work on as well. This is my first rodeo on creating a coin and everything was going smoothly for the first few days. It's going to take some time and research to figure these things out. So, in the mean time I'm going to pull down the official pools so I can have the time to figure this out.
Please be patient. I got thrown in to the deep end of this by a friend that pushed me to get this coin out there without a proper development time, testing, research, etc. I also want to thank everyone for throwing your hashing power at the coin, and the stress testers, seeing what it can handle. If this was a network attack then it definitely left a huge mark on the coin. I've never done a project like this, and I admit that it was slapped together way too quickly for even my liking. I'm hoping to have the time within the next week to untangle everything, figure out what went wrong, and get it released properly. Will I be able to save the current block chain? I have no idea. Will you lose all your coins? Who knows. All of this is currently in the air. If anyone has more experience than us and is willing to help us out we'd definitely be grateful.
If you guys have any questions feel free to ask. I'll answer to the best of my ability. Just so you know, I do have another job and this has already taken up a significant chunk of my free time trying to figure out the network issues, pool issues, etc., but I am dedicated to figuring these issues out and making this coin work. Definitely a huge learning curve in a language (C++) I don't use very often and never really learned that well.
Tux2
Dev,
Is joke i totally believe that.
The blockchain stuck at height 16370 and won't move forward.
Is joke i totally believe that.
The blockchain stuck at height 16370 and won't move forward.
Code:
12:38:09.114998 INFO ----- BLOCK ADDED AS ALTERNATIVE ON HEIGHT 16370
12:38:09.114998 INFO id: <9c4ef0b46f6828267982d82262bc7877fd8bff7dc01ce18839accf92c8fd6a73>
12:38:09.114998 INFO PoW:
12:38:09.114998 INFO difficulty: 709548
12:38:09.208799 INFO ###### REORGANIZE on height: 16370 of 16370 with cum_difficulty 11506721434
12:38:09.208799 INFO alternative blockchain size: 2 with cum_difficulty 11507431302
12:38:09.209278 DEBUG Key image already spent in blockchain: f360bab12b22ba6fc6b26f14464b8bfb2d6c25b583f381faa7367906123c5eca
12:38:09.209514 DEBUG Key image already spent in blockchain: 1e70fccf16a262de5bb8a3985c255a4000276f041a7b60bd9776fb8aaaadd614
12:38:09.209699 DEBUG Key image already spent in blockchain: bd5c3507a01dc54008a9f750acb585b58286bcba5ce194675247914762f3196e
12:38:09.209976 DEBUG Key image already spent in blockchain: d98712c532df432764cdd0b868dbb5e5d374198f9dce6a524a24f27bd2944b73
12:38:09.210307 DEBUG Key image already spent in blockchain: 6e03703781bf09f99cbde5d4bdcde882c71da0a7c6686e92f687695c13f51279
12:38:09.307383 INFO Failed to check ring signature for tx <856c1834da4683bb72a6a10038c597e98896cb1229e62ea447cc741e44388752>
12:38:09.307522 INFO Block <9c4ef0b46f6828267982d82262bc7877fd8bff7dc01ce18839accf92c8fd6a73> has at least one transaction with wrong inputs: <856c1834da4683bb72a6a10038c597e98896cb1229e62ea447cc741e44388752>
12:38:09.310748 INFO Failed to check ring signature for tx <856c1834da4683bb72a6a10038c597e98896cb1229e62ea447cc741e44388752>
12:38:09.310893 INFO Failed to switch to alternative blockchain
12:38:09.463443 DEBUG +++++ BLOCK SUCCESSFULLY ADDED
12:38:09.463443 DEBUG id:
12:38:09.463443 DEBUG PoW:
12:38:09.463443 DEBUG HEIGHT 16370, difficulty: 709548
12:38:09.463443 DEBUG block reward: 25.0300, fee = 0.0300, coinbase_blob_size: 160, cumulative size: 8662, 152(54/38)ms
12:38:09.464032 INFO Rollback success.
12:38:09.464159 INFO The block was inserted as invalid while connecting new alternative chain, block_id: <9c4ef0b46f6828267982d82262bc7877fd8bff7dc01ce18839accf92c8fd6a73>
12:38:09.464311 DEBUG [198.24.172.10:37373 OUT] Block verification failed, dropping connection
12:38:09.464477 DEBUG [198.24.172.10:37373 OUT] Interrupt connection
12:38:09.464617 DEBUG [198.24.172.10:37373 OUT] writeHandler finished
12:38:11.592984 DEBUG [118.25.12.142:37373 OUT] msg 1:1002
12:38:13.532296 DEBUG Connection to 46.126.95.96:37373 timed out, interrupt it
12:38:13.532587 DEBUG Connection timed out
12:38:13.532754 DEBUG Selected peer: 8087383566627567330 87.76.11.74:37373 [white=0] last_seen: d0.h7.m57.s14
12:38:13.532868 DEBUG Connecting to 87.76.11.74:37373 (white=0, last_seen: d0.h7.m57.s14)...
12:38:13.841879 DEBUG Connection to 87.76.11.74:37373 failed: TcpConnector::connect, connection failed
12:38:15.842334 DEBUG Selected peer: 13007404780682834648 198.24.172.10:37373 [white=1] last_seen: d0.h0.m0.s7
12:38:15.842579 DEBUG Connecting to 198.24.172.10:37373 (white=1, last_seen: d0.h0.m0.s7)...
12:38:18.194067 DEBUG [109.200.155.98:37373 OUT] msg 1:1002
12:38:18.501029 DEBUG [109.200.155.98:37373 OUT] msg 2:2007
12:38:19.601654 DEBUG [109.200.155.98:37373 OUT] msg 2:2004
12:38:09.114998 INFO id: <9c4ef0b46f6828267982d82262bc7877fd8bff7dc01ce18839accf92c8fd6a73>
12:38:09.114998 INFO PoW:
12:38:09.114998 INFO difficulty: 709548
12:38:09.208799 INFO ###### REORGANIZE on height: 16370 of 16370 with cum_difficulty 11506721434
12:38:09.208799 INFO alternative blockchain size: 2 with cum_difficulty 11507431302
12:38:09.209278 DEBUG Key image already spent in blockchain: f360bab12b22ba6fc6b26f14464b8bfb2d6c25b583f381faa7367906123c5eca
12:38:09.209514 DEBUG Key image already spent in blockchain: 1e70fccf16a262de5bb8a3985c255a4000276f041a7b60bd9776fb8aaaadd614
12:38:09.209699 DEBUG Key image already spent in blockchain: bd5c3507a01dc54008a9f750acb585b58286bcba5ce194675247914762f3196e
12:38:09.209976 DEBUG Key image already spent in blockchain: d98712c532df432764cdd0b868dbb5e5d374198f9dce6a524a24f27bd2944b73
12:38:09.210307 DEBUG Key image already spent in blockchain: 6e03703781bf09f99cbde5d4bdcde882c71da0a7c6686e92f687695c13f51279
12:38:09.307383 INFO Failed to check ring signature for tx <856c1834da4683bb72a6a10038c597e98896cb1229e62ea447cc741e44388752>
12:38:09.307522 INFO Block <9c4ef0b46f6828267982d82262bc7877fd8bff7dc01ce18839accf92c8fd6a73> has at least one transaction with wrong inputs: <856c1834da4683bb72a6a10038c597e98896cb1229e62ea447cc741e44388752>
12:38:09.310748 INFO Failed to check ring signature for tx <856c1834da4683bb72a6a10038c597e98896cb1229e62ea447cc741e44388752>
12:38:09.310893 INFO Failed to switch to alternative blockchain
12:38:09.463443 DEBUG +++++ BLOCK SUCCESSFULLY ADDED
12:38:09.463443 DEBUG id:
12:38:09.463443 DEBUG PoW:
12:38:09.463443 DEBUG HEIGHT 16370, difficulty: 709548
12:38:09.463443 DEBUG block reward: 25.0300, fee = 0.0300, coinbase_blob_size: 160, cumulative size: 8662, 152(54/38)ms
12:38:09.464032 INFO Rollback success.
12:38:09.464159 INFO The block was inserted as invalid while connecting new alternative chain, block_id: <9c4ef0b46f6828267982d82262bc7877fd8bff7dc01ce18839accf92c8fd6a73>
12:38:09.464311 DEBUG [198.24.172.10:37373 OUT] Block verification failed, dropping connection
12:38:09.464477 DEBUG [198.24.172.10:37373 OUT] Interrupt connection
12:38:09.464617 DEBUG [198.24.172.10:37373 OUT] writeHandler finished
12:38:11.592984 DEBUG [118.25.12.142:37373 OUT] msg 1:1002
12:38:13.532296 DEBUG Connection to 46.126.95.96:37373 timed out, interrupt it
12:38:13.532587 DEBUG Connection timed out
12:38:13.532754 DEBUG Selected peer: 8087383566627567330 87.76.11.74:37373 [white=0] last_seen: d0.h7.m57.s14
12:38:13.532868 DEBUG Connecting to 87.76.11.74:37373 (white=0, last_seen: d0.h7.m57.s14)...
12:38:13.841879 DEBUG Connection to 87.76.11.74:37373 failed: TcpConnector::connect, connection failed
12:38:15.842334 DEBUG Selected peer: 13007404780682834648 198.24.172.10:37373 [white=1] last_seen: d0.h0.m0.s7
12:38:15.842579 DEBUG Connecting to 198.24.172.10:37373 (white=1, last_seen: d0.h0.m0.s7)...
12:38:18.194067 DEBUG [109.200.155.98:37373 OUT] msg 1:1002
12:38:18.501029 DEBUG [109.200.155.98:37373 OUT] msg 2:2007
12:38:19.601654 DEBUG [109.200.155.98:37373 OUT] msg 2:2004
We had a network attack since only one pool was giving 99% of the hashing power to the network. This has now been fixed with us having 2 pools now! Our old one is at: http://fart.hashingmonkeys.com and our brand new one for the UK is at http://fartcoins.com/pool
My wallet is stuck at block 16369, the daemon is stuck in a loop with a bunch of messages about failing to check ring signatures.
Any ideas? Where is the blockchain/database stored? I may try deleting it and resyncing.
The blockchain is stored across different computers across the network. This ring error is due to only having one pool up, and is causing really bad payout issues. I'm in the process of putting up another pool to solve this issue. I've also brought down the other pool so that I can make sure we have the fartcoins to pay everyone if we have to roll back to that block again.Any ideas? Where is the blockchain/database stored? I may try deleting it and resyncing.
EDIT: oh, it's stored in .fartcoin in your home folder if you're looking for the local database.
oh ok ty very
and will be CPU mining ?
Yes, this is most definitely CPU mining. I started the network on a potato computer.and will be CPU mining ?
where did you found wallet plz ?
i just see CryptoNoteMiner.exe but isnt a wallet cant send and receive
any help or link for help plz
?
ps: ask for windows wallet or web wallet ty
We don't have a windows wallet yet, just Linux. I'm working on getting a paper wallet working. I have a working prototype with the wrong branding, I just want to make sure that I can successfully import it into the client (which means I have to write that as well) and then you can have a paper wallet. Once that is going we'll be working on a Windows wallet for you guys. However, right now I'm working on trying to get the official pool to actually pay out. We're having issues with the wallet on there that is getting fixed as we speak.i just see CryptoNoteMiner.exe but isnt a wallet cant send and receive
any help or link for help plz
?ps: ask for windows wallet or web wallet ty
dev because the balance is always outstanding and there are no payments that happens
We are actively working on this issue. Part of this is because we are the only pool and there is no competition. We are in the middle of setting up another pool for those of you in the UK so hopefully we can spread the hashing power out and get this pool to behave as well. Don't worry, I have everyone's account balance, and if needed we can always pay you guys manually. The pool was paying out just fine until around 12 hours ago, when it started having issues. I've been scratching my head, resetting the daemon, etc, but it keeps happening due to us being the majority of the network. Remember, this is a new coin, growing pains happen.Any way to generate a paper wallet?
Not yet, I'm currently working on that though.totally minable.
fart.hashingmonkeys.com
unfortunately I get an error:fart.hashingmonkeys.com
stratum connection failed:failed to connect to fart.hashingmonkeys.com port 4445: connection refused
Just so you know, the first 10 followers on Twitter to tweet @fartcoins with their address will get 100 fart coins in their wallet. https://twitter.com/fartcoins
No - the pool found it - I was in the pool - and I spoke with someone else who was in the pool- who got paid out on it,
But maybe you did not submit a share on that block? I got no benefit or FRT from the special block either - I was in the pool, but i don't think I got to submit a share on that block found.
Which is why I got no FRT from the finding of the special block found by the pool, even though I was on the pool mining actively at that time . I watched the block get found, - I was there !......"it was tense".......I even had my fingers crossed...
No Farting in the Pool ! Just kidding-
Maybe we can adjust the pool so everyone submits shares faster? Gives everyone a chance to submit a share for every block, or more of a chance to?
But if you're solo mining or mining in a different pool - then whatever the Official Pool Adjusts - will only affect people in the official pool at that time.....I would think...
TooT !
But maybe you did not submit a share on that block? I got no benefit or FRT from the special block either - I was in the pool, but i don't think I got to submit a share on that block found.
Which is why I got no FRT from the finding of the special block found by the pool, even though I was on the pool mining actively at that time . I watched the block get found, - I was there !......"it was tense".......I even had my fingers crossed...
No Farting in the Pool ! Just kidding-
Maybe we can adjust the pool so everyone submits shares faster? Gives everyone a chance to submit a share for every block, or more of a chance to?
But if you're solo mining or mining in a different pool - then whatever the Official Pool Adjusts - will only affect people in the official pool at that time.....I would think...
TooT !
Block 3700 "Special Reward" Block Found !
WeeHoo!
Congrats FartCoin !
WeeHoo!
Congrats FartCoin !
Someone stole it from the pool
Did someone solo mine it?what a reason to create this coin?
i don't know, someone mining coin's like this one?
i think people have resone to mining another things
lol, this is a joke coin, it's just for fun! Just like Dogecoin was. Also, we have an official mining pool now!i don't know, someone mining coin's like this one?
i think people have resone to mining another things
http://fart.hashingmonkeys.com
what algo?
It's Cryptonight/cryptonote based. Sorry about missing that bit of info in the post.
- No premine
- Cryptonight based
- It's a total joke!
- It's a fart coin!
- Definitely a scam
- A new block every 30 seconds
- 2,100,000,000 total supply
Block rewards
- 10 FRT per block for the first 8,640 blocks
- 25 FRT per block from block 8,641 - 48,960
- 50 FRT per block from block 48,961 - 135,360
- 100 FRT per block from block 135361 onward
Special Reward Blocks
- Block 37: 37 FRT
- Block 370: 370 FRT
- Block 3,700: 3,700 FRT
- Block 37,000: 37,000 FRT
- Block 137,000: 137,000 FRT
- Block 370,000: 370,000 FRT
- Block 3,700,000: 370,000 FRT
- Block 5,370,000: 537,000 FRT
Website is coming soon!
Please note that at the moment we are experiencing network issues/possible attack. The dev is currently working on it but at the moment we have no ETA as far as when everything will be resolved. Official pools are offline for the moment.
Fartcoin Official US Pool (Offline)
Fartcoin Official UK Pool (Offline)
Download Linux Client (Windows and Mac clients coming soon)
Twitter Account