I can't speak to the POS question, I only work on one part of the project, and SPECTRA will be having it's first release soon.

There are some dev installs here: http://dev.speccoin.com/

I'm still doing some testing with a couple of those chains but you're welcome to have a look.

I'm making arrangements for beta release of SPECTRA as I type.

Not sure if that will affect your decision

Themeless!  

I'm not a great designer but I've got quite a few hours into the default CSS just to achieve a generic but functional look. Designers will understand how that goes for sure. But I'm going to change the name from "Default" to "Themeless" now!

Seriously though, with that groundwork in place I hope some of you guys will be able to do great looking styles for this.

Architecturally, I've built in some text file inclusions so that non-coders don't have to get into the script code to adjust the headers and footers to suit, adding other elements around the 'working' bits will be pretty simple, as the page scripts invoke the block explorer functionality in, well, blocks for the most part.

And for those that will want to get into the guts of it and I've got a pretty good separation between the functional and presentation layers. All of the rendering code is centralized so you don't have to go hunting through every file in the package to find the parts you want to change.

I did a massive cleanup and re-factor this week and cut the size of the code base by over 50%, which just means 50% less places for bugs to hide. It's all very procedural and loaded with comments (can you have too many comments?) so hopefully everyone who is interested will be able to follow the code and do what they like with it. One thing about open source is you can't please everyone, but I hope in the end this tool will be seeing plenty of use, and fill a large gap in the current open source tool set.

I'm currently trying to load a HBN block chain into a SPECTRA database. 2.5m blocks of POS/POW hybrid block chain.  It's a bear, but since a couple of initial issues have been addressed things seem to be going smoothly, if not quickly.  

SPECTRA is working great with SPEC (basic POW only) and if it does well with a POW/POS hybrid (HBN) it should be fine with a fully POS chain as well I think. Soon it will be ready for a first release, and we'll see what kind of bugs other people can find with it. I'm sure there are a wealth of surprises waiting in the many available block chains.

I'm working on installation documents as well.  Ehh, well, I'm on the forum, 'cause who doesn't love writing documentation, am I right?

It's to the point where getting additional eyes on it is exactly what it needs. HBN is taking forever (it looks like it will literally take several days to load) so maybe we'll see about letting you guys have a look at the development server before that's fully loaded.

Updates Soon!

I saw the action on SPEC today, looked like some happy traders.

I'm getting started on my first project for the team right now, looking forward to exciting times!

 

It's been a while, bitcointalk...

I've been chatting with James for a couple of days now, working on this and another project.  So far it seems like a good fit, and it's nice to be a part of the team.

Here's looking forward to good things!


     ~ Jake

 

I would like some maples:

JCzCbjjLTHFtsx2ArqyPtV692NrCQAaPm8

thanks

This happens sometimes if you have been mining P2Pool, or other services which generate a large number of small inputs as well.  It's not a matter of the transaction amount, it's a function of the number of inputs required to generate a transaction for the specified amounts.  You run into the transaction size limit of the block chain.

If that's the problem, the solution is still to make smaller transactions. They will use fewer inputs so that your transaction fits within the maximum transaction size for the block.  Also, be prepared to see some large TX fees for these transactions.

In other news:

IFC Lotto ticket price is dropped to 100 IFC per ticket, from 1000.  A user here pointed it out to me, with a rise of nearly 10x in value, a ticket price decrease of 10x seemed in order. The tickets already purchased will be converted at drawing time into the appropriate number for your deposit.

http://lotto.coinworld.us/IFC/

And also thanks to TECSHARE for a nice bounty - I've added a new price converter to the Ticker Image API at cryptank.com.

You request an image with USD and the resulting price in IFC is displayed.

Simple instructions for use are at InfiniteCoinTalk.org.
More detailed instructions on the Ticker Image API are available at http://cryptank.com/ticker/

Because spots adjusts so quickly, some of the hash rate and difficulty figures seem, well, spotty.

It would appear that most of these issues are present in other coins, it's just not as noticeable that the figures returned for certain request methods are different across two blocks when it's something like every two thousand some-odd blocks with a coin like BitCoin. Very few people ever notice.

If you're not aware no wallet or client gives an accurate network hash rate, this is impossible.

By the same token, no pool can give you a truly accurate figure for the hash rate of it's miners.

Sometimes when the pool uses one estimation formula, and the client uses another, it looks odd. In both cases they're only estimates, based on past results and averaged out statistical figures. 

And they'll both become radically inaccurate if someone comes across a couple of lucky shares or blocks. Or if there's a particularly difficult streak.

Also an extra 800k spike in hash rate is typical when one of the hopping pools hits a coin.

It's big enough to see that my super duper mining machine will earn me some millispots if this ever hits a block lol

could definitely use help on this

He's not being trusting, he's trying to pay with a "Retractable" method of payment.

Selling coins for paypal payment is the "Trusting" side of that equation.

I don't see any me in this thread, heh

MH6TiuoqQfNc5u8FCs7KrhAyZh8BAnovh5

Got me, at this point. By manually manipulating transactions I've got some wallets with wierd balance info.  It doesn't sound like you've been (intentionally) doing anything like that.

Worst case if you just have to know, create a new wallet somewhere else and send it the coins.  It won't solve this mystery but you will be able to see where your coins are. Just about every exchange handles LTC if you want to use an exchange wallet for this you can pick one with more moderate fees.

Try these:

getbalance LQB9i8M95j7hhde19XZ8hnoxYS5bJiyXdz
getbalance LZd3jC3LkTT44hkFB4uqYboRcB5RzoWp8W
getbalance LUmrXVibufVSyDtEhJQTWT2DzEtN1sUBzA

to make sure they're actually empty.

I just downloaded the new litecoin QT - if you can't see your coins in those three accounts you could try the "listaccounts" command to see if there's another account there - then you would go through the procedure of getting addresses for that account and getting their balances too.

The empty quotes after the getaddressesbyaccount limits it to addresses that are in the default account of the wallet. But if you had ever labeled an address or something it may have created another account for it, as well.

That definitely implies that you have only the one address. 

Did you send coins to get from 695.84374004 to 400?  It would be odd if you had a single input for 295.84374004 and therefore no change addresses or anything. Though to be fair, there are quite a few branches int he "Satoshi-wallet family tree" and they constantly surprise me.

Try - getaddressesbyaccount "" - Those quotes are part of the command and will cause it to list addresses for the default wallet account.

Does that also show only the one address? Perhaps it's not displaying it's own change tx/address there or something.

You've got me curious.

The wallet uses multiple addresses without telling you.

Open your RPC console and enter the command "listreceivedbyaddress" that might help clarify things.

Coming to Coins-E?