Not the original ones, but we're on it.

Check us out at https://pay.withfedoraco.in and circle us at https://plus.google.com/114816033975093735144/posts

Offline Fedoracoin payments, now that's an interesting idea!
You should definitely leave that at http://feedback.withfedoraco.in/

Registered developers should have just received an email with some status updates!

Not registered yet? You can do so at http://dashboard.withfedoraco.in/singup

All done, you should be able to reach the website on https://pay.withfedoraco.in/ now!

Don't forget that we post these things on our G+ page: https://plus.google.com/114816033975093735144/posts
Circle us to stay updated.

Just a quick message for those trying to load the website and not succeeding - there's no need to worry, we're installing SSL certificates right now.

When we get back you'll be able to load w/ Fedoracoin over a secure connection!

They sure should

Contact us at developer@pay.withfedoraco.in to become a launch partner.

Don't forget to +1 and circle us https://plus.google.com/u/0/114816033975093735144/posts to show us your appreciation and support!

We're still looking for some site owners or developers that would like to work with us before our public launch!

Drop us a line at developer@pay.withfedoraco.in if you're interested, even if your site is small.

Reminder that you can follow news about us at https://plus.google.com/114816033975093735144 and that you can leave your ideas and feedback at http://feedback.withfedoraco.in/

Thanks! If you like us, be sure to share us.

Your support is the only thing keeping us going

You can now leave feedback for us at http://feedback.withfedoraco.in/

If you want to subscribe to our updates, you can do that at https://plus.google.com/114816033975093735144/

The current fanpage with 16 likes doesn't even have a username claimed - there is not reason to try to take that one over.
There's another one with 3 likes and no content that does have a claim to the username 'fedoracoin' though.

The max number of coins available isn't defined in a single variable, it's defined as a convergent series (which, in this case, converges to around 500B).

Guys, a quick teaser update from us to let you know that we're still active.

We're done with the first version of the actual payment processing.
It's still a bit rough-cut, but the proof of concept very much works.

In the first screenshot below, you can see our server logs just after the server got a payment to the inbox account of user 'test'.

That payment has not yet been confirmed, but we're logging it as 'seen'.

This way we can notify users of the Javascript Client-side payment flow through the use of websockets that we've received their transaction almost immediately after they've clicked send.

In the next screenshot, you can see the logs at a later time:

First, there has been one block since we received the first transaction, but said transaction was not in that block.
The next block did contain our transaction, so we detected that the transaction was now confirmed one time.

At that point, the balance is moved from the 'inbox' of user test to the wallet of user test.
Now, the balance will show up as 'unconfirmed' on the user's dashboard.

With each following block the transaction is confirmed more and after a certain threshold (settable by the site owner) the transaction becomes 'verified' and w/ Fedoracoin issues a callback to the website that the purchase was made on.
The transaction is now complete for the user, and they get the item they paid for.

After an additional number of transactions (we're still debating the exact number, but a payment processor should be reliable and actively battle double-spending) the balance becomes confirmed and user 'test' can withdraw the balance to a Fedoracoin address.

That's it for now folks!

Don't forget to visit the site/bump our threads if you want to support us!
If you have a reddit account, we'd appreciate it if you would help with spreading the word.

Guys, a quick teaser update from us to let you know that we're still active.

We're done with the first version of the actual payment processing.
It's still a bit rough-cut, but the proof of concept very much works.

In the first screenshot below, you can see our server logs just after the server got a payment to the inbox account of user 'test'.

That payment has not yet been confirmed, but we're logging it as 'seen'.

This way we can notify users of the Javascript Client-side payment flow through the use of websockets that we've received their transaction almost immediately after they've clicked send.

In the next screenshot, you can see the logs at a later time:

First, there has been one block since we received the first transaction, but said transaction was not in that block.
The next block did contain our transaction, so we detected that the transaction was now confirmed one time.

At that point, the balance is moved from the 'inbox' of user test to the wallet of user test.
Now, the balance will show up as 'unconfirmed' on the user's dashboard.

With each following block the transaction is confirmed more and after a certain threshold (settable by the site owner) the transaction becomes 'verified' and w/ Fedoracoin issues a callback to the website that the purchase was made on.
The transaction is now complete for the user, and they get the item they paid for.

After an additional number of transactions (we're still debating the exact number, but a payment processor should be reliable and actively battle double-spending) the balance becomes confirmed and user 'test' can withdraw the balance to a Fedoracoin address.

That's it for now folks!

Don't forget to visit the site/bump our threads if you want to support us!
If you have a reddit account, we'd appreciate it if you would help with spreading the word.

Guys, a quick teaser update from us to let you know that we're still active.

We're done with the first version of the actual payment processing.
It's still a bit rough-cut, but the proof of concept very much works.

In the first screenshot below, you can see our server logs just after the server got a payment to the inbox account of user 'test'.

That payment has not yet been confirmed, but we're logging it as 'seen'.

This way we can notify users of the Javascript Client-side payment flow through the use of websockets that we've received their transaction almost immediately after they've clicked send.

In the next screenshot, you can see the logs at a later time:

First, there has been one block since we received the first transaction, but said transaction was not in that block.
The next block did contain our transaction, so we detected that the transaction was now confirmed one time.

At that point, the balance is moved from the 'inbox' of user test to the wallet of user test.
Now, the balance will show up as 'unconfirmed' on the user's dashboard.

With each following block the transaction is confirmed more and after a certain threshold (settable by the site owner) the transaction becomes 'verified' and w/ Fedoracoin issues a callback to the website that the purchase was made on.
The transaction is now complete for the user, and they get the item they paid for.

After an additional number of transactions (we're still debating the exact number, but a payment processor should be reliable and actively battle double-spending) the balance becomes confirmed and user 'test' can withdraw the balance to a Fedoracoin address.

That's it for now folks!

Don't forget to visit the site/bump our threads if you want to support us!
If you have a reddit account, we'd appreciate it if you would help with spreading the word.

TIPS was designed especially to fill the need for a coin that isn't all about value.
The idea is that a TIP of the hat can be a compliment, thanks, whatever.

Once the block reward halves, we'll see a steep fall in supply and eventually some real-world value.

Only #fedoracoin seems to be really active, the other two are for when people decide to meet to talk about either development or marketing.
People don't normally idle there.

The good news is that, unlike #fedoracoin, they are actively moderated.

We already have #fedoracoin, ##fedoracoin-development and ##fedoracoin-marketing on freenode.
Please note that you are not allowed to use a single pound for channels that are not the main discussion channel for a FOSS project on freenode.

Sorry for triple-posting, I should have probably read the entire thread first

There's an Abe API up here: http://fedorachain.info/chain/Fedora/q

MystPhysX, theking7426, we'd like to offer hosting for the new site.

We don't plan on officially supporting it, since we have our own things to code, but I think the best thing to do from here is to fork this: https://github.com/icanprogram/fedoraco.in and make the text a bit more serious.
Then, we'll just host that repo for you.

If everyone is OK with that, I'll send nameserver info to MystPhysX

His name is icanprogram, he's also the guy that did the faucet front-end, like theking said.
Here's the source for the site, incidentally.

https://github.com/icanprogram/fedoraco.in