The LOGS STANDARD

This area is under construction.

Please NOTE:

BLOCKLOG borns as backend-logs reader, a problem much wider than the simple blog-problem.

Some example of dapps back logs:

EXAMPLE 1:

Admin1 adds John Doe to Contract3 as admin

in this example, admin1 is a wallet address, John Doe is a wallet address, Contract3 is acontract address, admin is a specific permission, and could be a string or a number identifiyng the role.

resuming: [address,address,address,uint]

EXAMPLE 2:

Owner changed fees in market2 to 5%

[address,"fees",2,5]

EXAMPLE 3:

Admin1 added a room with name "Plaza" and tag "open" in contract 3

[address,1,"Plaza","open",address]

Every contract need a personal standard for logs, and this must fit the solidity language and his limitations (your log can be made of 10 informations, since you must be able to read the log in one shoot via a constant function and then render it on the page!)

BLOCK LOG borns to answer to this problem and adapt to any log interface automatically (under construction)

IF you simply want a PERSONAL BLOG, with swarm things will be much simpler: you just post a swarm address and you keep there your post-data, the reader will pull everything form there.

At the moment you can use THOT in order to deploy a simple BLOG. THOT will also index your blog at BLOCKLOG INDEX. This is a completely open system, and BLOCKLOG aims to be the referring official reader (the first and only so far!).

BLOCKLOG has nothing to deal with your blog.

Decentralized blogs are a SENSIBLE thing!

BLOCKLOG aims to become a famous READER, not to be closed by major force!

I can't delete your blog from the blockchain, it is impossible, but I can apply censorship at BLOCKLOG INDEX.

Nothing personal.

In case I may decide to push the whole index out of BLOCKLOG page, so I will avoid any kind of problem to BLOCKLOG itself.

Thanks for understanding.

More to come.