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'.
![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2F0XW3nUE.png&t=665&c=jgacttLq-7A9Jw)
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:
![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FKGAbqqx.png&t=665&c=8xEkT8X-ak-cpA)
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.