maxxflyer edited this page Feb 12, 2017 · 19 revisions

Welcome to the BLOCKLOG wiki!

BlokLog is usually introduced to the public as a Blogging Platform. Actually it is much more, and has a basic importance in the management of future Ethereum Dapps you will interact with.




The story behind BLOCKLOG (and its smart-contracts):


At the beginning I had a set of smart contracts working together, and a bunch of SUSPICIOUS users.

During the night I have the chance to make tricks and to substitute one of the modules, and then put everything back in place before morning.

In a situation like this, your community needs transparency. They can always check the blockchain with a blockexplorer, but not all the people are really expert, and what happens if you need to track 10/100/1000 dapps where you keep your money or you make your business?


Step 1 - I had an idea: I will put a simple "logs memory" inside the smart contract. The contract will produce a log EVERY TIME A SENSIBLE OPERATION IS PERFORMED, keeping it visible and available to all the public, without the need to visit a blockexplorer of any sort.

What are these SENSIBLE OPERATIONS we talk about?

Example: you run a huge market, and you decide to change the basic fees (that's a huge change in your market), and you communicate it to all your sellers in your platform. They all jump to a block explorer to see the transaction you performed and to check what you do. This rare but IMPORTANT kind of events must be always tracked, beeing a SENSIBLE PROBLEM.

Example 2: you have a set of smart contracts working together, and a community relying on them, and when you substitute one of the contracts you can make tricks. The act of substituting one of those modules, is a SENSIBLE OPERATION.

Similar situations exists in DAOs ,where someone may have the key of some modules (the developers? the admins voted by the community?), and the community needs to track their actions.


Step 2 - The second step was to create a VERY STANDARD BACK END I will put in all my dapps.

All my customers, jumping from one dapp to another, will recognize my standard BACK-END-LOGS-READER and will feel more comfortable.

Now they will be faster in tracking my dapps-back-ends, since they don't have to digg inside a blockexplor any more, they just see a clean TRUSTLESS list of SENSIBLE OPERATIONS directly via backend.

All other transactions aren't saved into the logs memory, for those, you can use a blockexplorer.


Step 3 - The third step was to bring this concept to the extreme level, and to publish the BACK-END-LOGS-READER and the STANDARD LOGS-MEMORY-CODE (few raws to copy/paste at the end of your contract) and make it available to all the commmunity.

Now, using the BACK-END-LOGS-READER, you can watch any standard-logs-memory, and actually you can do more:

You can follow them like you follow people in twitter!

Now you can really track 10/100/1000 dapps-back-ends, and every time someone performs a SENSIBLE OPERATION you will easy see it via your BLOCKLOG READER. You aren't going to spend your life on a blockexplorer anymore!


Step 4 - Later, I asked myself what would happen if you take the standard LOGS-MEMORY-CODE (to be copy/pasted in your dapp) and you simply put it in an empty contract.

Oh, well... since the contract is empty, it isn't going to produce any log... but of course... you could push in some logs manually.... and here you go! now BLOCKLOG is the most open BLOGGING system on the Ethereum Platform.

You can use THOT to generate your standard blog. Your blog will be an independent contract controlled only by you. Humanity can now access it via Ethereum Wallet, or more comfortably with BLOCKLOG READER, the first and coolest OPEN LOGS SYSTEM on the planet.

BLOCKLOG can be used also to manage your Blog and make new posts (logs).

You may think at BLOCKLOG as something similar to twitter, but with a difference. In Twitter all accounts are inside Twitter and belong to Twitter. In BLOCKLOG all accounts are spread on the Ethereum blockchain and belong to their owners. BLOCKLOG transforms Ethereum into a an Open Cloud Of Personal Blogs. In Twitter you have a home where you follow people, in BLOCKLOG you have 2 HOMES (!!) , one in order to follow PEOPLE, the other one in order to follow sensible DAPPS BACKEND LOGS.

Remeber, there is a big difference between the open standard with its emerging independent network and the READER system named BlockLog. BlockLog has no Database. It is just a reader, a door. You can always manage your blog directly with the Ethereum Wallet. Or, in the future, use one of the 1000 existing access doors (or build your own!).

Later, once swarm will be accessible, your blog will be ready to deposit your post-content there. At the moment, while everything is transforming around us, BLOCKLOG already offers you a basic solution.

BlockLog is going to integrate a TOTAL TEMPLATING PHYLOSOPHY interface, according to which all blogs and all posts and, more generally, all Etherum Entities will have a chance to get a "visual skin". An ICO is going to be launched at the beginning of March 2017.

Open now your first PERSONAL, AUTONOMOUS, INDEPENDENT, DECENTRALIZED BLOCKLOG Blog, and make your first step with me into the future.


(BlockLog is based on AlphaLayer)

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.