People had been concerned about the preservation of authenticity, and proof of time of existence of their ideas, before the time when an insecure browser and the web could peep into.

Proof-posting works with most of the known blockchains, and you can even enter a custom blockchain of your own.

Improved the feeds summary a bit.

To increase the signal-to-noise ratio for first-time visitors of the home page, I have hidden menus, and compacted operations, so as to let the eyes focus on content.

However, apparently, some people didn't like it, because it is not clear what to do, so, I mostly reverted the change.

It is now possible to lock targets, create teasers for investment, and share them with potential interested parties.

I implemented a hash that takes previous data and current column and the previous hash to produce a hash of the entire database.

This allows us to synchronize with the minimum of data transmissions when I write the synchronizer part which shall rehash all its own data, then retrieve the hash of a binary search of the sorted data.

I spent a few hours working on the remainder of this problem and got documnent retrieval working after finishing save document.

This lets you save and retrieve JSON documents

The document data inserted is also queryable by SQL.

Joins against documents are not yet supported but I plan to implement this.

Most computers use locks to synchronize, which are very slow. This design is far faster and allows locks to be elided for performance.

I use unscynchronized data structures and achieve 100 million requests a second raw communication performance for a cost of 10 nanoseconds per batch of messages.

I managed to store a JSON document and I used the SQL inserter to insert the document. In theory the object is queryable by SQL

{ "items": [("name": "item1"), ("name": "item2")], "subobject": {"subobject_key": "value"} }

• Now, target owners can decide when target is ready for investment, and investment is not ready by default.