There is a couple of differences. On the document certification side, Trustatom doesn't upload documents to the server unencrypted (it doesn't upload them at all at the moment, but there will be an encrypted vault functionality). Besides that, Trustatom makes use of private keys known only to the user so that only the user can prove their submission at a later time. Lastly, there is also a private fingerprint mode that helps avoiding putting file's fingerprint to the blockchain as is (for others to discover). What Trustatom lacks comparing to BlockSign right now is the ability to add a visual signature to the file.

On the grander scale of things, Trustatom's functionality is not limited to certification. It already has joint escrow functionality (escrow without a third party) and there will be more coming.

Does this answer your question?


Thanks!

Hi,

Somebody once said to me "smart contracts are like high school sex, very few have actually done them..." and I realized that the moment one steps out of our little nice bubble, even the very term "smart contracts" raises eyebrows. (Heck, even inside the bubble, while people generally know what it is about and what it is for, very few have actually engaged in those types of transactions.)

This was one of the reasons why earlier this year I've started a new company, Trustatom. The idea was to build ready-to-use, highly specific smart contracts and market them across different markets. We've started with document certificates (an improved version of proof of possession) and joint escrows (escrows without a third party). Some interesting announcements are in the pipeline.

The product is still in its early beta (and certainly has some rough edges, some of which are already known and some are yet to be discovered , and I wanted to give the bitcointalk community the opportunity to help shaping the product that's being marketed to users primarily outside of the core Bitcoin community. Any feedback is really welcome!

You can sign up and try it out at https://trustatom.com

Cheers,
Yurii
https://angel.co/trustatom

What: Lets talk about practical and futuristic contracts enabled by cryptography & blockchain. What is needed today? How do we see smart contracts evolving in the future? This is a public seminar with the goal to identify and discuss most practical and most revolutionary applications of the smart contracts technology.

When: Aug 30, 10AM PST

PANELISTS (more names to be announced soon):

Oleg Andreev (CoreBitcoin)
Stefan Thomas (Codius, Ripple Labs)
Tim Swanson (Great Wall of Numbers)
Yurii Rashkovskii (Trustatom)

Reserve your seat: http://gowoa.me/i/Fj5

Hi,

I've recently presented (https://www.dropbox.com/s/gsd6lkxhue1dkjm/bitcoin_wallet_api.pdf) an experimental project at the Inside Bitcoins HK conference.

The project is called Bitcoin Wallet API (http://bitcoin-wallet-api.github.io/) and is aimed to provide a uniform, privacy-oriented, restricted access to user's Bitcoin wallets to enable web applications seamless integration with the Bitcoin infrastructure. Think geolocation or camera API for HTML5, but for Bitcoin.

The project is still in its early days and I've published a rough spec draft (http://bitcoin-wallet-api.github.io/spec/) and made a timestamping demo (you can find a screencast on the homepage).

The reason why I started this project was my personal realization that often, in order to provide non-standard transaction features, web app developers have to go as far as developing a new wallet app so just that their users can sign those transactions. What if there was a way to securely connect web apps and wallets (without exposing private keys)? Would that help new, sophisticated bitcoin web apps go to market faster and have much easier onboarding strategy?

I'm looking forward to your feedback and I'll be happy to answer questions, if any.

Thanks!

Hello everybody,

A small experimental project of mine resulted in something small & working and I wanted to share it with you.

The project is called Bitcoin Wallet API (http://bitcoin-wallet-api.github.io/) and is aimed to provide a uniform, privacy-oriented, restricted access to user's Bitcoin wallets to enable web applications seamless integration with the Bitcoin infrastructure. Think geolocation or camera API for HTML5, but for Bitcoin.

The project is still in its first days and I've published a rough spec draft (http://bitcoin-wallet-api.github.io/spec/) and made a timestamping demo (you can find a screencast on the homepage). While I've released the source code for the demo (https://github.com/bitcoin-wallet-api/demos/blob/gh-pages/timestamp/index.html#L56-L107), I need another session to polish the Chrome extension before open sourcing it (it's very rough on the edges). The screencast is shot with this extension.

The reason why I started this project was my personal realization that often, in order to provide non-standard transaction features, web app developers have to go as far as developing a new wallet app so just that their users can sign those transactions. What if there was a way to securely connect web apps and wallets (without exposing private keys)? Would that help new, sophisticated bitcoin web apps go to market faster and have much easier onboarding strategy?

I'm looking forward to your feedback and I'll be happy to answer questions, if any.

Thanks!

Update: I've pushed out the initial proof-of-concept extension implementation (https://github.com/bitcoin-wallet-api/bitcoin-core-chrome).

Y.

Bex.io's mission is to proliferate Bitcoin across the planet and we're achieving this by working with trusted partners in various countries. We continuously provide them with the most cutting edge technology & services and enable them to be a bitcoin business of choice in their country.

We're looking to add a talented operations engineer to our team. You'll be a key member of the team and ultimately responsible for managing our distributed deployments across the globe: infrastructure, application deployment, monitoring and recovery management. You will be able to make a lot of decisions that will affect the quality of our service.

Our company's culture is built on continuous learning, being cutting-edge (hey, we even wrote our own provisioning tool!) and we all share a great deal of passion about Bitcoin.

Responsibilities

* Identifying best matching hosting partners
* Managing server infrastructure
* Writing and maintaining application deployment / system orchestration scripts
* Making sure the system is pro-actively monitored 24/7
* Paying attention to security (we're dealing with money!)

We [so far] use such tools as: Docker (docker.io), ZFS on Linux, Erlang/OTP, PostgreSQL, Splunk, Hypnotoad, Riemann. This is the beginning of a very interesting journey. As we evolve, so will our infrastructure, the key element of our business.

Please apply at http://jobs.bex.io/apply/0UWVgC/Senior-Operations-Engineer.html

Decided to push an interim update to the site, it no longer refers to the pricing plans mentioned above. Instead, it outlines the structure.

BTCLuke and becoin, thanks for your advice. Just as a side comment, Bex.io deployments are not centralized nor happen to be in Canada.

greBit, as I said above, the pricing will be figured out individually for every scenario. It's not going to be exactly what it is on the site right now — for some exchanges with higher commissions (there are still exchanges that charge a couple of percents; it all depends on the market) and lower volumes our commission is likely to be higher, while for other exchanges it is likely to be quite lower.

There are many *arguably hard* parts of running an exchange. Regulations/banks/AML/fiat transactions — of course. Security — no doubt. Marketing — absolutely. And many, many others.

That said, thanks for your input. Highly appreciated.

We at Bex.io are working on achieving a variation of this objective. Even though we are starting with individual exchanges running on our platform, we will be enabling cross-exchange order filling, effectively enabling a global liquidity pool. It is not strictly a P2P exchange, rather a backbone that allows trustworthy representation of non-digital assets.

It will be interesting to see future developments in the exchange space.

The pricing structure published on the web page will be soon updated to reflect its true state.

Basically, the pricing model is still the same, which is a percentage of the revenue with a minimum (which, admittedly, still isn't explained clearly on the web page).

Now, the percentage will vary depending on a client-per-client basis, depending on their unique circumstances — which is the market they are in, the volume they will be booking, risks, etc. Needless to say, the higher the volume is, the lower is the fee.

The "minimum" part is also quite simple — it's a base fee that gets covered by the percentage fee. If your percentage fee is lesser than the base fee, you only pay the base fee. If it is equal or greater, you pay only the percentage fee. Basically, your total is "the greater of base fee or percentage fee"

Is this clearer? Hope it is! Please don't hesitate to ask if you still have questions.

Hi,

Although I am sure some of you already hard about our project (http://bex.io) on reddit & HN, we wanted to reach out to even a larger audience with the announcement.

In a nutshell, we're developing a Bitcoin Exchange as a Service product that will allow Bitcoin entrepreneurs go to market quickly, while focusing on what's really important — regulations/licensing, bank relationships, marketing.

We're expecting to launch by the end of this summer. We have a long term vision on how to take this from individual exchanges to a global liquidity pool and beyond.

As of right now, our matching engine can process MtGox’s daily volume in a matter of minutes — and we'll be working on making it even better to catch up with the future market growth. Our system uses a subset of the industry standard for the real-time electronic exchange of securities transaction (FIX 5.0).

We're employing many security practices (secure multi-level cold storage manager, signed cash account transactions, key derivative functions for passwords, OS-less nodes, encrypted communications, audit trail, OWASP security guidelines adherence, intrusion detection, regular threat and vulnerabilities analysis, KYC API integration, etc.)

Our offering also includes a backoffice UI & API, as well as a reference customer UI with API.

The pricing on the web site will soon be updated. With what we have learned over the past month is our pricing will vary, depending on the market and volume served.

We already have a few customers signed up. We invite you to join the first cohort, grab a time to chat with us: http://meetme.so/bexio

If you have any questions, please feel free to email us at hi@bex.io

P.S. If you want to stay in the loop on our progress, we will be sending periodic updates over the coming months, just subscribe at http://bex.io/.  We will also be at the Bitcoin 2013 conference in San Jose from May 14th to 21st if you want to meet in person (we’ll be also doing some sneak peak previews!)

The last bid is 5 seconds late ;-)

5.3 BTC — bex.io http://bex.io/

5.1 BTC — bex.io http://bex.io/

Who are these people? All I can easily trace is it's a Pakistan-based operation.

Hi,

I am a software developer and entrepreneur from Vancouver, BC — we're started doing quite a lot of work in the Bitcoin space recently!

Yurii.

I doubt it is really on anybody's radar in those echelons... too small of a threat. Not in a political sense, no. Not yet.

Hi!

You can learn about blockchain size without having a fully downloaded one as well using this chart https://blockchain.info/charts/blocks-size