Where can I find the source code?

Usually a coin is mined or minted through an ICO. Why do we find both ways here?

Hello, is there any bitcointalk thread link about your bounty? How will you monitor the progress of the bounty campaign and is there any spreadsheets available now?

I can't see anything wrong with the white paper you created either.

What do I have to do to see the Selfllery token in my wallet?

Hi, does your project have any notable partnerships at this stage?

What revenue plans is the company to fulfill after the ICO is over?

Will the company issue its own payment cards?

Where can I watch the video about your technology?

What criteria will be used for affiliates to become a member?

Do you have agreements with any exchanges now?

Hello everybody! What is the minimum buy?

What will be your way to deal with copyright protection (DMCA)?

Will you please make your algo clear to beginners? Especially the specifics of your contracts)

Have you already started to cooperate with any new companies?

Where are you physically based out of?

Harambecoin is definitely not dead yet - I've been doing dev work but a lot has been somewhat "behind the scenes" so to speak, which is why it looks like right now the area that I could use the most help in is promoting/social media so if anyone wants to be a part of that, we can definitely work out a bounty.

Anyway here's a quick off the cuff list of what has been done since I've last posted:
- harambepool.com's web front-end was down for a few days after my VPS was restarted even though the pool and daemon were still working properly; this is fixed now.
- If anyone had tried to join the #harambecoin IRC channel, I assume someone had tried to take over the channel and set it to invite only. This is fixed so come on in - I'll try to check in as much as I can.
- The new release is ready and has been uploading to harambecoin.com. This is v1.0.0.3 and has the added checkpoints, DNS seeds, and the new Multisig prefix (which will become more relevant soon). Anyone looking to get harambecoin or using the release version, an upgrade is reccomended:

http://harambecoin.com/downloads/harambecoin-core-win-v1.0.0.3.zip

http://harambecoin.com/downloads/harambecoin-core-linux-v1.0.0.3.tar.gz

http://harambecoin.com/downloads/harambecoin-core-osx-v1.0.0.3.tar.gz

**NOTE: The osx version was experimental - I think there may have been an issue with bdb when I created the .dmg bundle. Since I don't have a Mac, if someone could give this a try and let me know one way or another whether it's working or not it would be appreciated.

There's a couple things I'm working on right now: rebuilding the test suite, rolling forward the code to the new build system, and also a multisig/blockchain insertion project I've been toying with so if anyone can help with giving me some input from a code perspective, there is definitely a lot to be done.

Also I mentioned the logo was updated but don't think I ever posted it on here:

Bounty for what?? Yes, there is a fund for development but there's no set list so suggest some ideas of what you would like to contribute or at least a general area of work and we can try to figure out something.

Also, the previous 10k bounty for the ongoing web development and the new logo was paid in transaction 439aa8f9acd001f2962bb651460c52594d8a5f14155cf4622d4e121044accd11

Been a while since I've given this an update so just want to mention a few things. First, a new release will be coming within a day or so - for the most part this will be just minor things: additional seednodes, checkpoints, a facelift of some of the images, a new logo, and all build issues fixed for OSX and newer (16.04) Ubuntu. That aside there are two larger decisions that may cause issues in some (hopefully) rare situations.

First, I realized that I made a mistake and for only the Linux binaries for v1.0.0.2 are compiled with libdb5.1 while windows uses 4.8. I thought about which version to use for this next build (and forward) since it should be the same for all platforms and seeing how the standard will soon be 6.x. That said, I can't think of any major benefit they provide and since after this set of changes I plan to forward merge up to the newer build system so that we can use the same static dependencies as bitcoin, it makes sense to just use 4.8 in all platforms moving forward. So basically anyone using the linux binary will have to create a new wallet and transfer their coins to a new address. I really don't think there are many linux users who don't just compile from source and since there aren't a huge amount of users at this point anyway, I don't think this should be that widespread.

Second, changing the multisig address prefix from '3' to 'M'. I know this was suggested for litecoin, but I don't think it was adopted yet because while it's not a 'hardfork', it definitely could be problematic for balances in multisig addresses. So here, the last I checked there are no multisig addresses being used so I feel like the best plan is to just update this now before they are. Let me know if anyone can see any problem with this, otherwise that's the last change I'm going to push before I prepare the next release.

Bro you need to relax - seriously, you posted the only two dedicated nodes (one of them is hardcoded seednode) when it was asked and no one has mentioned it since so I don't think it's a huge issue. In the upcoming version there will be extra dnsseeds so hopefully it doesn't even come up again.