Getting started about haskoin-core HOT 15 CLOSED

Hello xavier83,

This project is at a very early stage at this point. It consists of both a specification, that we haven't yet started work on, and a Haskell implementation, that we're actively writing at this point, but it's not functional yet. Please participate. This is blank slate. What would you like to work on?

Cheers

from haskoin-core.

I have started reading the source and got it to run successfully under ghc. To my understanding, the current version just connects to the testnet and parses the messages and stores blockchain. I would like to know where is blockchain stored and in what format. I would like to implement code for finding peers or add more peers. I have been reading more about iteratees and enumerator lately.

from haskoin-core.

Hello Xavier,

We're not even storing the blockchain at this point. We've just partially coded the protocol definition. We still even haven't figured out how we're going to go about it all. This is right now at "figuring out how we're going to go about this" stage.

Feel free to code in your tree, and send us push requests for things you add. Beware though that this is a state of flux right now. Things will break badly quite often. It isn't really ready for anything. Consider it just a toy for the moment.

Cheers

from haskoin-core.

I am happy to start early on this project :)

from haskoin-core.

That's great, I wish you good luck.

There are some changes that are being done at this point, especially near the main function. Beware that anything you do at this point will probably not merge cleanly. You probably want to create a separate module to put your peer handling code.

Cheers

from haskoin-core.

Btw, what are the goals of the project? is it just a reference implementation/ to be a feature-rich alternative to other clients?

from haskoin-core.

Hello alaudidaelark,

The goals have somewhat evolved over time. At first it was meant to be a mostly didactic implementation, to accompany the Bitcoin specification that we're meaning to write. Then it became evident that since Haskell allows for very safe code, that is also easy to run in multi-core setups, that we should focus on making it a fully functional (no pun intended) implementation, for actual use.

There hasn't been any talk on how feature-rich the application will be, we're still struggling with the basics here. Neither of us are longtime Haskell programmers, and we're learning as we go. It's still premature for us to think about features.

I wasn't expecting so much attention at this stage, this is kind of cool. Any suggestions on the technical side would be greatly appreciated, especially if anyone happen to have a clear idea about how you'd go about writing this in idiomatic Haskell.

from haskoin-core.

Our primary goals is correctness and cleanliness, expressing the problem in the most sensible manner. No premature optimization shall creep in, especially if such a thing would hurt the expression of the problem at hand. In the true Haskell spirit, we would like to make something that looks and like a clean —albeit complex— mathematical formula.

from haskoin-core.

Any plan to formally verify the implementation? That would be awesome. :P

from haskoin-core.

That sounds like a lot of work for a lazy person like me. :)

from haskoin-core.

Hi, Is there a proper communication channel, where I can reach you guys? irc/email?

from haskoin-core.

Yes, email me to [email protected].

from haskoin-core.

According to my mail-service , apparently the domain xeno-genesis.com doesn't have mx record. :S

from haskoin-core.

Your mail service isn't working properly, because I have a very nice mx record there.

from haskoin-core.

Hey guys. I will close this issue for now. Please feel free to contact me by e-mail and I will help you get started with Haskoin.

from haskoin-core.