BBQcoin is not worth selling at the moment. Once upon a time it went for some nice prices, I am not sure what happened, maybe the people who bought millions then dumped them at a loss later or something, or maybe it is just that the number of coins minted per day is a larger supply than the demand demands lately.

It is a pity as it was pretty nice for a while, I saw them sold for up to seven bitcoins per hundred thousand. I hope the people who bought in lots of 100,000 at a time back then didn't end up dumping them at a loss but who knows, maybe they did.

-MarkM-

Maybe it is the other way around: the price is way down because people are dumping lots of coins.

So instead of asking why are people dumping so many when the price is so low, try asking why the price is so low when people are dumping so many, which is maybe a less difficult question to answer.

I suspect people were just oblivious to their IXCoins in the past, maybe still are, like they dump when they see they have lots accumulated maybe instead of when they see a good price to sell them for. In essence maybe they arent' caring about price, they assume all altcoins are worthless and pick a day to sit down and dump their accumulated (e.g. from merged mining) altcoins regardless of whether some coins happen to be having a good day or a bad day that day. Its sell my coins day so I sell for whatever people are paying today kind of thing?

Re D&T's point about 13,000 more coins every day that is not going to go on forever, it ends relatively soon, IXCoin is not a forever-minting coin like DeVCoin, GRouPcoin. GeistGeld and (maybe?) CoiLedCoin. Someone said some time ago there was less than a year and a half left of minting, though I didn't check their math to see if they were right.

-MarkM-

Maybe you should ask in the new user section of the forums, as maybe by the time users are able to post here they consider themselves veterans.

-MarkM-

I tried p2pool again, and sure enough the pool side does seem to see most of the expected hashing power.

But the display on the web interface. version 0.97, is showing 195 gigahash whereas on mmpool it usually showed 282 or so.

So the web display is making it look like it has more problems with p2pool than p2pool actually thinks it has...

-MarkM-

So they are putting some kind of "it is our machine not your machine" crap on it to prevent it mining coins they do not "authorize" or something like that

Taking a percent too, maybe? Maybe forcing you to have to use their pools thus not be able to mine coins they choose not to support

TL;DR How the heck do they plan to prevent people using them to mine whatever coins the user chooses to mine, and WHY

-MarkM-

cgminer can do that too.

You can activate specific USB devices with command-line args too if you know which devices they are.

-MarkM-

I tried mining on Cryptominer and a while ago I had one point smething coins of confirmed earnings, now it shows zero confirmed earnings.

That seems like worse than just bad luck... The pools are not mining on the main chain to such an extent that a 200+ block re-arrangement took place or something

I had not mined 13 hours though so maybe it was that they had not set 200 blocks as the confimation threshold? So maybe my coins still are in the acocnt its just that now the code realises they are not confirmed yet?

-MarkM-

Its presumably not real hours, but, rather, block-hours, that is, the number of blocks that ought to correspond to two hours if in fact the blocks were being created at the target rate... In other words, 120 minutes divided by 4 minutes, thus every 30 blocks. When blocks come fast, it thus happens faster, when they come slow, it presumably would come slower... Same applies to years in bitcoin's supposed four years between block reward changes and so on and so on...

-MarkM-

Well no hurry eh, they took forever to release it so now we can take forever to get around to reacting to that fact.

-MarkM-

Oh yeah right, sorry, I meant that but my fingers fudged it it seems, sorry.

To those worried that coins aren't confirmed after 175 blocks, someone posted earlier in this thread that maturity is at 200.

-MarkM-

My TagBond ID is 4245

Here is my address: TWSNX6zGDjJ6ecmvR6xTo7wiqGy8MesJNj

-MarkM-

My Saturn's cgminer has been mysteriously dying every day or two, the web interface just shows it as dead I have no idea why, so I just restart it.

I have grabbed this new ckolivas binary to try hoping it will not similarly decide to die from time to time.

-MarkM-

I seem to have temporarily caught up with the blockchain now, though I guess it could easily turn out to go off on a fork again at any moment.

Here is my address: TWSNX6zGDjJ6ecmvR6xTo7wiqGy8MesJNj

-MarkM-

Ripple sounded interesting at first, but after a while there was just too much "opportunity cost" in waiting day after day after day for the code.

So I pretty much had to forget about it and move on to other things.

That applies both to all the gateways I wanted to set up and to the various people who were interested in the possibility of being able to run their own currency without the vulnerabilities of a blockchain.

Sure some day month year or decade I'll likely get around to looking at it again but now other things have been taken up so there just isn't spare time to screw around with Ripple, plus of course the whole delay delay delay crap put a bad smell on the whole thing that leads to even wondering whether what they finally did release will turn out to actually work.

(Afterall as far as I know the gateway code included still isn't fit for real use, is it?)

-MarkM-

Eventually with those latest given nodes I did get the chain up to block 696 but now I has been stuck there.

Seems like the chain is horribly fragmented or something, eliminate one bad fork and you just end up on another?

-MarkM-

receive version message: version 70001, blocks=706, us=142.68.215.183:61879, them=173.23.156.175:8623, peer=173.23.156.175:8623
received block 0000000005c290608a7c
ERROR: AcceptBlock() : prev block not found
ERROR: ProcessBlock() : CheckBlock FAILED
Misbehaving: 84.44.228.21:8623 (0 -> 10)

-MarkM-

I used addnodes for all the nodes someone listed earlier which were shown as not being incoming connections, since anyone who connected out to them rather than being connected out to by them might not have their port open. Thus I have a buch of nodes all of which presumably have their incoming port open.

As I don't have my own incoming port open here at home I only have eight connections, all outgoing thus all ones that have their incoming port open.

Nonetheless I am stuck on block 500 even though that list of nodes was given earlier in the thread as a supposed solution to being on the wrong fork...

-MarkM-

You could make a RIpple-clone.

-MarkM-

Even bitcoin itself did not have wallet encryption back when Ixcoin was created.

So there was no wallet encryption code to merge.

Right now it would not make much sense to update Ixcoin code without basing it on I0Coin's new code, so that it gets the RAM usage problem fixed as well as encrypted wallet and all kinds of recent bitcoin bugfixes and so on and so on.

It should be pretty trivially simple, just a cut and paste of I0Coin, changing the handshake bytes the ports the block / difficulty timing the name the images and so on just like making any other clonecoin.

It might cost a little more than a from scratch new coin simply because you don't just want a cut and paste job done you also want to make damn sure the result is exactly the right ports and handshake bytes and IRC channel and difficulty rules and genesis block and so on: the ones Ixcoin already currently uses.

-MarkM-

On Masterchest.info I see


Two comments on that:

one: I thought Mastercoin was actually going to be minting more coins

two: s/tread/thread/

-MarkM-