I'm Joining Back in on the Action at
Hasher BEN Pool:
http://ben.hasher.ca Let's Get Ben On a Roll !
I saw you this morning buddy, nice to see the # of hashers rise for the 1776 Spirit.
Yes, it's a humble blockchain, but one with a future set firmly in the past. Huzzah! Slowly, pennies at a time, just as Benjamin Franklin would tell us to proceed. It takes years to build something decent, and he would know.
Yes is it very slow, these last block have been murder except for one on which we got lucky.
But, there are 2.5 million Ben and mostly the goal should be to protect the blockchain from the robo traders and the hater-pools that live to wreck coins. I know them well in regular stockbroker form or the new iteration of geek form, pump and dumpers are the bane of regular investors (families and common folk I mean).
I am glad this coin is not proceeding that way, it is better to have grass roots and slow progression, as if gently growing a fragile plant. It's not better to have a team of devs, because a lot of them have no common sense. It is better to have as we do, a team of likeminded regular people, who have a desire to make something new, and who have suitable opensource code, with which to work. We are in a good position, in terms of slow, steady growth and interest. Well except Ben the Dev who seems to have lost interest unless Ben is made to merge mine? I am glad Ben isn't merge mined it totally violates the spirit of a block chain, completely. I am amazed that anyone involved with any blockchain would advise sharing proof of work, that's absurd. But like I said, others can explain why they also don't like merge mining.
though there were a LOT of coins dumped at .00004 and so I love the way things are going: More miners getting interested, even after this coin has been hit hard by dumpers.
The "same" devs minus Benjamin it seems, recently designed CC to be a tough coin to mine --but we already have that here. So I am rolling my eyes as I see some of this. I guess they'll make a nice pump off it, or maybe his silly face is silliy enough to wrangle to doge miners? Hehe, no way will the dogies be happy with .1 coin per hour, hehe. Plus his coin is gonna get smashed by the shorts once its usefulness has lived on. [shrug] We will see if Colbert has a brain or can he only make jokes? Definitely he is the ultimate joke of a man, so we shall see if he has anything but jokes.
I look forward to the future, but I mine Benjamins on principle, in the 1776 spirit. When the flashes and pumps and dumps and ETFs and fake Enron like companies and shitty IPOs all fade away, I will be mining the Benjamins blockchain, assuming I have internet and electricity. One thing I'd like to do is to build a radio packet-IP type localized experiment so that Benjamins mining network can endure outage of power and internet. Radio-based IP is a big interest for me, because all the ISPs are basically worthless puppets now. So loss of Internet will be a future problem, and of course bitcoin will be mined by the milspec servers in the artic for 1000 years, we little common Benjamin folk will have to figure out how to keep our blockchain up and our coins useable, when there is no Internet. In the future I mean. If there's revolution I mean. Like, I am trying to prepare in the 1776 mindset as well as mine.
edit
Oh this blurb across the top of the forum says" "News: ♦♦ A bug in OpenSSL, used by Bitcoin-Qt/Bitcoin Core, could allow your bitcoins to be stolen. Immediately updating Bitcoin Core to 0.9.1 is required in some cases, especially if you're using 0.9.0. Download. More info."
...So can we figure out how to fix this in the Ben client, or that something Ben also doesn't know how to do? God this Open SSL was definitely sabotage in the form of sewing weeds. So where is the code in the BTC client and shalln't we make the same adjustment to the Ben code? Ben, do you give even the smallest of f*cks about your work?
edit
Okay so bitcoin QT does not use JSON-RPC but rpcssl=1 made some people nervous, but the client is okay, we assume (until we commoners become skilled 'nough to ken the code fully). However all servers are the true target, because lazy server admins will have big problems. So anybody running any server already knows by now that heartbleed is bi directional, in that the attack can go either way, servers can be used as weapon and also malware will be adding this little needle to their toolkit. Screw all malware authors, just f*cking die already you d*cks.
Anyway I got worried when bitcoin upgraded, because we can use abandoned code if there is no major flaws in it. But I haven't found any data to suggest the QT client uses JSON-RPC OpenSSL though there is a setting for it, it doesn't use it. *whew* but server operators better all rotate certs and force password resets and monitor their servers like a hawk. http://www.reddit.com/r/Bitcoin/comments/22gq5e/heartbleed_bug_major_openssl_vulnerability_could/