Posts made by zerodrama

PR for whom?
The purpose of a forum is to serve the needs of the forum.
That means understanding and preventing BS like UNOCs.
Remember when BTC ppl discussed sketchy crap in secret.
Let’s not be in secret.
@mirrax

Also Orwellian.
@mirrax

Factom is a prettier version of Link
@mirrax

cough link cough
@mirrax

Yo da.
@mirrax

I am thinking of getting back into this thing.
Where is it now that cryptsy crapped itself?

yeah but we still a cleanup on isle 5. I imagine everything still points to ‘Bitcoin’ instead of ‘Feathercoin’. The UI updates are nice but as noticed, only the windows exe made it to .9.5, not the master branch. The master branch is still missing the UI changes. There is a lot of cleanup to do with bitcoin branding that was left behind with feathercoin master branch.What work Ive done, Ive lost with recent backup failures. I am in need of GitHub WRITE access. Furthermore we have a FREEDOM issue here that has recently been brought to my attention.

Although Debian and UBUNTU both use SSL, namely OPENSSL, it has one fatal flaw: current implementation is NON-FREE as distributed.

Fedora team have made changes to FREE it, however, these changes remove the code we need to function.(Elliptic curves)

Several Bitcoin-esque projects are affected, as they ALL use openSSL.

Noted HERE: http://forums.fedoraforum.org/showthread.php?p=1581297 and HERE: http://mikeminneman.com/2013/12/getting-dogecoind-to-run-on-centos/

The CentOS pactch doesnt seem to make any changes. However, it is noted that there is further work to be done on HARDENING as noted in this patch:

https://github.com/weex/bitcoind-centos/blob/master/makefile.new. Current version with Fedora is 1.0.1k (pull from 22, 21 sources are broken).

Ive noticed severe DATA LOSS occuring on Debian systems with Jessie. UBUNTU introduces bugs that shouldnt be. I cant use either as a result.Looks like Im rebuilding OPENSSL…EDIT: NO GO. EPIC FAIL. I dunno how to proceed now. Bitcoin team uses a static version of openssl included with thier app, so does litecoin. Perhaps we should follow suit.

ALSO:

Packages for Feathercoin for Fedora(and Im sure others) are missing the qt wallet client.This is a HUGE oversight. We need to include both the daemon AND the client.Please repack.

It’s not a license issue.

It’s a patent issue.

Use it.

And if Certicom does something nasty, start a riot.

so delete:

if(ECDSA_verify(…

…

return false

and add:

bool CKey::Verify(…

…

return ret

}

is that right?

ok so 102c is safe? or does it require changes to code?

The team didn’t check that issue.

Do you have a link to the description available?

Feathercoin uses the openssl libraries as Bitcoin does, so there is a risk, that the same issues will occur.

If you have a static build of the feathercoin wallet, you should be safe, as the libraries are compiled into the program.

If you compiled the wallet to dynamically load the libraries at run time, the risk is given.

This is from 5 months ago: Openssl bump by theuni Â* Pull Request #5634 Â* bitcoin/bitcoin Â* GitHub

Openssl had a change and it causes problems in Bitcoin. The update can invalidate the chain.

Does ftc have that issue? I’d like to update my packages on Linux, but that stops me from doing so.

Kevlar, any pointers on generalizing the cryptocoin format so

1. coins can be libraries

2. wallets can be scriptable themes

would be welcome.

My health is a little better and I am getting back in this thing. I think what happened to us in the before times rattled me a bit.

As for slack, I tried maintaining the #feathercoin channel on freenode, but web is taking over everything, because well installing and configuring stuff is getting worse.

Cue Hitler finds out video…

Publishers are a dime a dozen. Obsolete.

Miners are a peculiarity of protecting the bridge everyone’s crossing over so as to preserve the value of the transferred item.

Mess with the bridge and you mess with the people who trusted you to do the job.

I’m interested in a new coin erryday, but I can’t even stomach ever getting into the mining game again.

Kevlar, you confuse ability and relevance. I’m all for a research chain.

Let me give you a different analogy:

The coder has a hammer.

The miners have a blueprint.

The market wants the house built quick.

The holders want to add a swimming pool.

The coder has a tool. The miners say whether the swimming pool will fit without renovating. The holders have a goal. If the miners screw up the blueprint, the holders are very much entitled to moan about it.

The power each one has effectively is an accident of the madness that we call software development. The attention each deserves is more fluid than that.

All protocol changes should go to the back burner.

We need momentum not band-aids.

This isn’t a programming course.

This is about the cryptocoin code.

Also people pay for prompt attention to questions.

Crypto coins use C++, but I’d like to also look at Javascript and Python. I like Ruby, but Diaspora was a distribution disaster because of it.

If ppl want to see the code explained with actual samples, then I’ll accept FTC as payment.

Covered: Feathercoin, Catcoin, Confcoin, and Virtconf.

So how do you want to do this?

We’re not getting anywhere unless we get in the code and everyone understands it.

Also I am going to temporarily decouple from USD and charge based on the average price in the last something or something months.