Brickblock will be represented by a smart contract that runs on the blockchain, which handles broker registration and manages individual PoA contracts.

Abstract This document describes a smart contract platform built on top of a globally distributed computing network such as Ethereum or Rootstock. The suggested Proof-of-Asset (PoA) scheme will enable users to seamlessly trade tokens, which represent di erent types of foreign assets on all ERC20 compatible markets. 

The basic idea is to create a number of PoA contracts, each representing a di erent foreign asset. By linking the token contract to a digital trust fund (DTF), there will be a near 1:1 coupling between the value of the token and the foreign asset. Users can purchase PoA tokens in exchange for native currency, trade them, or hold them and receive a share of any dividends that the asset pays out. 

Investors may redeem their PoA tokens, prompting the DTF to liquidate the corresponding foreign assets and refund their current market value in native currency.

Overview During a contribution period, Brickblock tokens (BBT) will be distributed among participating contributors. Brickblock tokens can be traded on any market, or locked up in order to generate so called access tokens (ACT)Access tokens are required to pay the fees for operating PoA contracts and keeping them alive over time.

Proof-of-Asset tokens represent a certain foreign asset available to trade on the Brickblock platform. The assets backing those tokens are held by a pulicly auditable digital trust fund. All these tokens implement the ERC20 speci - cation and are seamlessly tradeable on compatible third-party markets.

Figure 1: The di erent types of tokens, and how they interact

Brickblock Token (BBT) 

The Brickblock contract itself implements an ERC20-compatible token, which will be distributed to the contributors of our fundraiser. In addition to being tradeable, these tokens are needed to generate new access tokens.

Access Token (ACT)

Access tokens are required to pay fees to operate PoA contracts and keep them alive. They can only be generated by locking BBT into the access token contract. While BBT are locked, the contract will credit new ACT to the senders account. The rate at which ACT are generated increases over time while the BBT are locked. Generated ACT can be withdrawn at any time, however, doing so resets the age of the locked BBT that generated them. Access tokens are required to operate certain functions of the PoA contracts, and are destroyed upon use. The PoA contract will notify the access token contract of the user's address and the number of ACT required. If the user has enough tokens in his or her account, then the requested amount will be subtracted and the operation will be allowed to continue. If the balance is not enough, then the call will throw an exception, preventing the PoA contract from executing the requested function.

for more info on this project, visit the link below

Website : https://www.brickblock.io/index.html
Whitepapers:https://www.brickblock.io/Brickblock_General_Whitepaper.pdf
Facebook :https://www.facebook.com/brickblock.io/
Twitter :https://twitter.com/brickblock_io

Profilename BTT : Gis15

My ETH : 0xAd2E59d183E4D68249851851F275309181658c28