If groups do that with groupcoin. Isn't there an arbitrage opportunity by mining or buying GPC? How do they value the GPC high enough to avoid arbitrage?
GRP can be merge-mined with bitcoin. on the bad side its a memory whore  |
|
|
|
No, those are source-code tarballs, so you can compile them however you want. -MarkM- Can you say command to install from package groupcoin wallet? can you extract it and read README + doc/build* or is this tomuch to ask for? |
|
|
|
|
mine of course too (see signature)
|
|
|
|
according to CC, anything he says is written into stone, if he says hes new update is official then it must be "official", so sad... |
|
|
|
This makes for some nice drama reading, but the question remains.
I guess I was not not privileged enough to get any notice of a hard fork (For those that do not know I own/run bbq.cryptocoinexplorer.com).
AFAIK I am the only working block explorer for BBQ. The explorer linked to on BBQcoin.org has been frozen since JULY. (478500 2013-07-04 15:31:38)
These leaves me in tough situation, and I am tempted to take down the explorer until this matter is settled, as there now seems no consensus on which client/chain is the official.
well my Abe has BBQ too ( http://darkgamex.ch:2571) and neither i nor figroll have been notified. nobody has been notified at all nor any information alike. i (as almost anybody else) will stick to the actual bbq, not some stolen shit (just like bbqcoin.com tried back then) |
|
|
|
The way I find out whether a coin is updated, usually, is simply to go through all my coin source directories doing a git pull on each. The ones for which the git pull pulls new code are evidently updated. Now though it is sounding as if there might not even be any particular github repo that is the one updates are pushed to  -MarkM- nope it seems to be closed source?! |
|
|
|
|
yea, there wasnt much going on. id had some things i wanted to fix/backport but all i got "nice you working on that" but no "ok, merge it"...
|
|
|
|
What are you guys doing? You seem to be the ones that want to break BBQCoin and stop it from getting upgraded and move forward.
Bigduab you don't run BBQcoin.org so you cannot make decisions for it. And we are still to wait for your android wallet.
Why are you now going to the exchanges as a non Dev and telling them what to do?
All clients get updated and lots of users have already downloaded and started using the new client and you are trying to make it so that any coins they mine will be useful.
Your not a client development Dev so please stop acting like you are. Please.
Im sry but you cant call yourself dev by changing pictures and reading wiki's how to do changes to coins/copy changes from other coins... What you did is worse than bbqcoin.com (He didnt wanna hardfork, you do. Your also PreMining, he didnt). You didnt even inform your (ex) dev-team (figroll + me) about what u planned to do, all we got froum you is big talk, no game. Look what you have become, if you understand what you did you would be ashamed of yourself... If you want to play shitcoin game -> stay with extremecoin, crimecoin and all the other things you copy pasted. You also said you got a seednode which is a lie, basicly you just made a public bbqcoin daemon and gave everyone its IP. a seednode (DNS Seeder) is something completely different... PS: this had to be said |
|
|
|
Talked to Jimmy at CryptoCoinTalk.com he has hidden the BBQCoin forum untill we get this worked out. At least no one will stumble upon the upgrade from there.
thanks, you got my support  |
|
|
|
The BQC client update that CaptChadd sent out on October 4th (via Cryptocointalk.com) will put you on a fork that is unsupported by all exchanges, pools and blockexplorers. If you have already upgraded please revert back to the official client found on sourceforge http://sourceforge.net/projects/bbqcoin/. -bigdaub What was said here about the exchanges saying it is unsupported is not true. I have emailed the exchanges and have an open ticket with one. The only reason this client update has not been widely adopted was due to lack of communication with this forum being down. BBQCoin Client Version 1.1 on BBQcoin.org is the mandatory client upgrade with more upgrades in the future with more seed nodes, checkpoints etc. When the exchanges do change to the new client anyone still using the old one could lose coins. The sooner you upgrade the safer you are. I have done all I can do now to let everyone know. All I ask for is trust. I believed in BQC enough to buy a website and help to bring it back from the dead. Now I am slowly going to modernise the client and get the interest back. All I ask for is trust. I believed in BQC enough to buy a website and help to bring it back from the dead. Now I am slowly going to modernise the client and get the interest back. Yes yes CC we know you have been with BBQ from the beginning. Before it was on any exchanges. BEFORE it was worth anything. You have spent your own money on a website  Your self proclaimed martyrdom for BBQ does not license you to do whatever you want. Releasing a wallet update that creates and instant fork without any warning is probably the dumbest thing you can do! When the exchanges do change to the new client anyone still using the old one could lose coins. The sooner you upgrade the safer you are. So basically you are pre-mining your own update! Nice... BBQCoin Client Version 1.1 on BBQcoin.org is the mandatory client upgrade with more upgrades in the future with more seed nodes, checkpoints etc. If this was the case you would set the hardfork to happen in the future, giving everyone at least two weeks to upgrade before the fork. Not release the client when the forum that most everyone uses is down. What are you going to tell Cryptsy when all* coins deposited and exchanged over the last four days disappear from their wallet? *edit - all coins moved over to cryptsy from the start of the hard fork will go back to their owners. Giant double spend! if nobody upgrades, let him play his game. aslong ppl stay with the correct client, no harm done. yes i suggest to just ignore this "not mandatory upgrade", its all about who has the longest chain afterall... |
|
|
|
The BQC client update that CaptChadd sent out on October 4th (via Cryptocointalk.com) will put you on a fork that is unsupported by all exchanges, pools and blockexplorers. If you have already upgraded please revert back to the official client found on sourceforge http://sourceforge.net/projects/bbqcoin/. -bigdaub seems he went insane... |
|
|
|
LevelDB is designed for hard disks, not SSDs. It's not only about writing blocks when they arrive but updating the databases too.
So I imagine this is more of an issue with SD cards then? I think most SSDs have wear levelling (hence they're used for all sorts of IO intensive operations, and often for databases with few issues). this is a issue of any NAND device so far, "wear levelling" is just a nasty workaround (which often dosnt work well) |
|
|
|
|
be aware that this is a sure way to kill your SD Card
|
|
|
|
When doing the "make" command, I get this error:
quark.c:91:13: warning: right shift count >= width of type [enabled by default
quark.c:91:13: warning: right shift count >= width of type [enabled by default
quark.c:91:13: warning: right shift count >= width of type [enabled by default
quark.c:91:13: warning: right shift count >= width of type [enabled by default
thats a warning not an error! as its a warning you can ignore it, i had the same and had no problems so far. |
|
|
|
i was interested in this coin until i noticed the op was using windows Windows? what's that?  I think you mean winblows.. And I can't stand that shit - Cross-compiling from <3Linux haha, whats up with the screenshots from the op?? it must have just been one of your windows beta testers huh i tried cross compiling. apparently my ancient ass bios doesnt support virtualization cross compiling needs no virtualization... |
|
|
|
Lol, you OCers are a different breed of cat! You wait 9 months for your Jalapeņos and proceed to blow them up.
I'm just giving you some good-natured grief and I feel bad for the few who've lost or damaged their Jallys. But for us less daring individuals it can difficult for us to understand why you'd even take the risk in the first place.
With difficulty rising so quickly, wouldn't it be wiser just to mine with it straight out of the box instead of modding and experimenting with firmware hour after hour, day after day? I start to freak out if my ASICs have any downtime. For example, I just setup 6 ASICMiner Blades a few days ago and during the first night, the PC that was running Stratum Proxy had a Windows update and restarted. I about cried when I saw my stats. Hell, I get mad if one of my USB Erupters goes offline for 5 minutes, lol.
if you know what you do, you wont damage your jala at all  changing source can be done without taking the jala offline, if you do it right you dont even have to disassemble the jala for flashing it. flashing takes 2-3 minutes spending 1 hour offline time for the jala is totaly worth it if you gain alot more hashpower. |
|
|
|
Hi,
This might not be exactly "on subject" but:
I have built and am running perfectly anoncoind/i2p on debian test, a total breeze, highly recommend debian test (as long as you keep away from the mac wannabe gui and use gnome classic )
For those trying, i just cracked building the anoncoin-qt for Linux.
cd ~/anoncoin # the dir where that git created
qmake USE_UPNP=- BITCOIN_QT_TEST=0 -o Makefile.test anoncoin-qt.pro
make -f Makefile.test clean
make -f Makefile.test
ssh root@localhost "cp $PWD/anoncoin-qt /usr/bin"
Hopefully helps this someone cos i sure looked hard for the instructions but to no avail.
I do not see many anoncoin-client I2P nodes there yet ... so the more building the i2p/linux the better i say
why not just sudo/su instead of "ssh root@localhost"? also i suggest using xfce |
|
|
|
There is supposedly some clever elliptic curve math trick that can be used to generate vanity addresses without knowing the private key, I think.
But one might not be able to do it using the "vanitygen" program.
It is probably related to the methods used for the extended deterministic wallet system that lets you not only generate new addresses for customers but, farther than that, give a customer a number/code from which that customer can generate new addresses, of yours, to send payments to, whenever they like, with your wallet still being able to recognise the payment is to you, and maybe also to know which customer that (series of) address(es) was given to.
So basically from a private key you generate some special elliptic magic thing, that you give to the vanity site, it generates addresses all day and night on and on until it finds one that is vain enough for you.
So maybe no need to give up the basic concept, you just need to do it in a "secure" way.
-MarkM-
vanitygen works with the split-key your talking about |
|
|
|
This update does not influence to connections. But last few days I has only 1-2 connections. I don't know what happened with other nodes, but my nodes are working fine. Try to rerun you client. If it doesn't help, try to manually add nodes by the 'addnode' command with the following addresses: bhqfvosghsfdbi3qubnk3ro6juklz5w7b6l3x6mibkxzzk3mob5a.b32.i2p
z5pg37axylu7wuncppbzvwxawb5mo3euxuwbyi2s2um7bhnl3caa.b32.i2p
ofa7kfuqewnxyqiadnsj6ibcwtj6ndcabwcfabljmuyol2pussaa.b32.i2p
mzvsw6bwae6ul33b5zege5xie2cevno6vgik6nrb6lw74cn3wmdq.b32.i2p
After the update manger on Xubuntu downloaded the official updates then I ran your exe's it works OK. Just got three I2p peers within five minutes. Edit: Soon up to four peers. exe's? are you running it in wine? wtf... |
|
|
|
|
Show Posts
