Topic: BBQCoin, the coin you want to eat. - page 57. (Read 143498 times)
well i not tried rucoin so i not seen the chat interface etc... shall have to dig that out then... and yeah that would be pretty cool... i just switched my 7750 GFX card over to it... am getting 72Khash or so atm just as a spot comparison what u mining on?
I think seeing if BBQcoin can survive this time around is a good test.
Are you mining BBQcoin right now? I am doing just to get the transactions quicker.
How about adding a chat interface like with Rucoin? And being about to write messages into the chain?
Are you mining BBQcoin right now? I am doing just to get the transactions quicker.
How about adding a chat interface like with Rucoin? And being about to write messages into the chain?
Cool, so we are all one the same chain which is great news.
This is going to be such a fun coin. It does not need value with regards to the USD but can be more like a powerful and indestructible hobby coin.
Cheers for the 2000.
Move out of the way Novacoin, here comes BBQcoin.
This is going to be such a fun coin. It does not need value with regards to the USD but can be more like a powerful and indestructible hobby coin.
Cheers for the 2000.
Move out of the way Novacoin, here comes BBQcoin.
Yeah I agree... is by far my favourite named coin
and yeah i don't care about it having a $ value, is good to test solo mining on and familiarizing yourself with cryptocurrencies without loosing $$.Was thinking would it be worth looking into patching the source code to see if we could test storing torrent files in it like has been shown can be done with namecoin here?? -->https://bitcointalksearch.org/topic/save-any-files-to-namecoin-blockchain-145278
or would it be best to leave the BBQ to just cook the sausages
Your most welcome on the 2000 BBQ's
... there are some people who switch on BBQcoin and let others connect to them, but u have to set up BBQ coin in a particular way to do that... believe markm explains in this thread how to do it... but basically people will turn off the client.. and there a VERY small user base... i never had more than 3 connected peers.. i on 1 atm
How come there are only 2 active connections now? There were 7 connections this morning.
Cool, so we are all one the same chain which is great news.
This is going to be such a fun coin. It does not need value with regards to the USD but can be more like a powerful and indestructible hobby coin.
Cheers for the 2000.
Move out of the way Novacoin, here comes BBQcoin.
This is going to be such a fun coin. It does not need value with regards to the USD but can be more like a powerful and indestructible hobby coin.
Cheers for the 2000.
Move out of the way Novacoin, here comes BBQcoin.
OK just got home from work and blockchain all caught up...
I have received 3 donations today..
one for 37 at 12:08,
one for 7.70 at 12:09 and
one for 26.78 at 12:20...
Were these u chad?? If so gtz it looks like u on the same blockchain and ur 10's of thousands of BBQ coins are valid... throw me an addy an i'll put a shrimp on my BBQ for u and send u some back to show it all works smoothly
I have received 3 donations today..
one for 37 at 12:08,
one for 7.70 at 12:09 and
one for 26.78 at 12:20...
Were these u chad?? If so gtz it looks like u on the same blockchain and ur 10's of thousands of BBQ coins are valid... throw me an addy an i'll put a shrimp on my BBQ for u and send u some back to show it all works smoothly
They were not me but I have just sent you 1000 BBQcoin, so please let me know if ya get them mate?
My address is bHPKWVpzptrTE1hN3MekGrm7WauqeLnjZZ
Thanks
Sweet yes 1000 BBQ received... and I threw 2000 back at ya
BBQcoin resurrected? 
Looks like it to me, the hashrate are growing, transactions are working aswell as solo mining.
Things are looking up for BBQcoin.
OK just got home from work and blockchain all caught up...
I have received 3 donations today..
one for 37 at 12:08,
one for 7.70 at 12:09 and
one for 26.78 at 12:20...
Were these u chad?? If so gtz it looks like u on the same blockchain and ur 10's of thousands of BBQ coins are valid... throw me an addy an i'll put a shrimp on my BBQ for u and send u some back to show it all works smoothly
I have received 3 donations today..
one for 37 at 12:08,
one for 7.70 at 12:09 and
one for 26.78 at 12:20...
Were these u chad?? If so gtz it looks like u on the same blockchain and ur 10's of thousands of BBQ coins are valid... throw me an addy an i'll put a shrimp on my BBQ for u and send u some back to show it all works smoothly
They were not me but I have just sent you 1000 BBQcoin, so please let me know if ya get them mate?
My address is bHPKWVpzptrTE1hN3MekGrm7WauqeLnjZZ
Thanks
BBQcoin resurrected?
OK just got home from work and blockchain all caught up...
I have received 3 donations today..
one for 37 at 12:08,
one for 7.70 at 12:09 and
one for 26.78 at 12:20...
Were these u chad?? If so gtz it looks like u on the same blockchain and ur 10's of thousands of BBQ coins are valid... throw me an addy an i'll put a shrimp on my BBQ for u and send u some back to show it all works smoothly
I have received 3 donations today..
one for 37 at 12:08,
one for 7.70 at 12:09 and
one for 26.78 at 12:20...
Were these u chad?? If so gtz it looks like u on the same blockchain and ur 10's of thousands of BBQ coins are valid... throw me an addy an i'll put a shrimp on my BBQ for u and send u some back to show it all works smoothly
If when one fires up the daemon, even with -rescan flag, it does not check checkpoints in its existing already on disk blockchain, then I suppose it is possible that my node simply has not actually checked its blockchain against that new checkpoint.
I cannot remember now exactly what I did that finally got me a second node up and running, maybe I simply copied over my ~/.bbqcoin directory as ~/.bbq-privnet so maybe my second node that I fired up to check I could connect okay also ended up not actually checking that checkpoint.
I wonder how I managed to copy the hash wrong though in the first place. It was a copy/paste operation and correct number of bytes so presumably it must be the wrong block's hash. I have made checkpoints a lot of times, I thought I had it down that the height shown in the debug.log a few lines after the hash of the block is the height pertaining to that hash.
I guess I'll have to try again, see if I can do it right this time.
Do any of the allchains-explorer type sites feature a BBQcoin-explorer?
-MarkM-
I cannot remember now exactly what I did that finally got me a second node up and running, maybe I simply copied over my ~/.bbqcoin directory as ~/.bbq-privnet so maybe my second node that I fired up to check I could connect okay also ended up not actually checking that checkpoint.
I wonder how I managed to copy the hash wrong though in the first place. It was a copy/paste operation and correct number of bytes so presumably it must be the wrong block's hash. I have made checkpoints a lot of times, I thought I had it down that the height shown in the debug.log a few lines after the hash of the block is the height pertaining to that hash.
I guess I'll have to try again, see if I can do it right this time.
Do any of the allchains-explorer type sites feature a BBQcoin-explorer?
-MarkM-
Can I check to make sure that I am on the same chain?
Can someone give me an address to send some BBQcoins to please who can then report back that they got them?
Can someone give me an address to send some BBQcoins to please who can then report back that they got them?
hit me up chad.. i have successfully exchanged some coins with nethead and markm and a few others so we all on the same chain for sure
bWnUiCU3MGxjKBFifHEtvXLjSq33wMFHbt
Can I check to make sure that I am on the same chain?
Can someone give me an address to send some BBQcoins to please who can then report back that they got them?
Can someone give me an address to send some BBQcoins to please who can then report back that they got them?
EDIT: if ur compiling it, be sure to remove the latest checkpoint. #86425
I don't think that is actually necessary, really?
What does your block 86425 look like and what is its hash? Is it actually different?
I think there is something other than those checkpoints that is causing connects to be dropped and so on.
I had a hard time just getting a second instance on my same machine to connect to my first instance. But finally after changing the order in which I started them up I got them to connect.
If you recall we did compare what block we were on etc, plus also I have recieved coins osmeone (maybe even it was you?) sent so it did seem we are both on the same chain, which should not even be possible if your block #86425 differs from mine.
-MarkM-
as soon i was at this block, all cons got droped and new connections couldnt be established.
EDIT: maybe the release on SF containts a wrong checkpoint hash?
I did do any of this node stuff.
I just ran the client in server mode, started my solo miner and then mined 30,000 BBQ.
By tomorrow I should be on about a million with both my miners on it all at once.
Its a very nice fun coin, maybe we could play some small betting games with it or something?
It is a fun coin after all.
I just ran the client in server mode, started my solo miner and then mined 30,000 BBQ.
By tomorrow I should be on about a million with both my miners on it all at once.
Its a very nice fun coin, maybe we could play some small betting games with it or something?
It is a fun coin after all.
EDIT: if ur compiling it, be sure to remove the latest checkpoint. #86425
I don't think that is actually necessary, really?
What does your block 86425 look like and what is its hash? Is it actually different?
I think there is something other than those checkpoints that is causing connects to be dropped and so on.
I had a hard time just getting a second instance on my same machine to connect to my first instance. But finally after changing the order in which I started them up I got them to connect.
If you recall we did compare what block we were on etc, plus also I have recieved coins osmeone (maybe even it was you?) sent so it did seem we are both on the same chain, which should not even be possible if your block #86425 differs from mine.
-MarkM-
use the default ports
afterwards just wait and u get connected to my public node.
EDIT: if ur compiling it, be sure to remove the latest checkpoint. #86425
Code:
rpcport=19322
port=19323
EDIT: if ur compiling it, be sure to remove the latest checkpoint. #86425
I'm sure if you ask MarkM nicely he'll tell you some nodes you can get the client to connect to
One person told me one, in private message, that I use with -addnode. But that was in a private message, and my own node has no incoming port, sorry. Set yourslf up with an incoming port though and people should find you, and if they don't then give out your own node's IP and port for others to use -addnode to tell their nodes to reach out to you.
-MarkM-
this was one of the nodes i connected to:
"addr" : "174.58.242.26:19323"
hope it helps
"addr" : "174.58.242.26:19323"
hope it helps
I'm sure if you ask MarkM nicely he'll tell you some nodes you can get the client to connect to
Jump to: