Struggling to Interface in a Digital World

The 2016 paper published by NSPE, "Blockchain Technology: Implications and Opportunities for Professionals Engineers" states that, "today, the institution of professional engineering is struggling for an interface with the digital world."

It's odd to think that engineers of all people are struggling to interface in a digital world. While that is less true today than in 2016, the construction industry is still the least efficient among all businesses today.

The rate of acceleration between licensed professional regulations and the remainder of the world is staggering.

This construction industry exposes us to increasing rates of risk.

The Security Approach Has Changed Little Since it Was Invented.

Which Stamp is Easier to Steal?

Let's qualitatively examine the security between a physical engineering stamp and a DocuSigned signature as a stamp.

• DocuSign: You'll have to pass through two-factor authentication to log in. To steal this signature, you need the password and the physical device used for the second authentication point (usually a phone).

• Physical Stamp: Google their license, buy a stamp online, and stamp a drawing.

We are not advocating DocuSign as the solution. However, this demonstrates that our industry is so far behind that we'd sooner have the system hacked than learn new engineering techniques which could solve many of our problems. Taken at its extreme, this unwillingness to act could be a violation of the .

Engineering Supervision Does Not Require Physical Proximity

A surprising number of states attempted to address the growing virtual world we live in and how that even impacts the meaning of "direct supervision." Laws today were written for offices of yesterday when an engineer was physically in the same space with the unlicensed staff.

The regulations in our industry give off a tone of either someone that genuinely wrote them in the 80s and forgot ever to update them or someone that still thinks the internet is a fad.

Either way, it is entirely untrue to say that engineering can only happen when two or more humans physically share a room during the process. Meanwhile, are permanent remote work companies.

A Permanent Supply & Demand Problem

Each state's laws provide authorities to organize a board of directors. The board has varying power, usually reviewing and approving licenses and issuing disciplinary actions.

With one board for each state, that leaves us with only 50 board of director groups to regulate in building construction. We can't expect that level of responsibility to fall on that small group of people. We have technology that can solve these problems (more on that later)

Assuming we live in an ethically perfect world, this is still too much work for one person to manage directly. How can we reliably track this level of complexity in a way such that public safety is dramatically improved?

These protocols worked when the industry's technology was born onto paper and lived on writing until the completion of the project.

Our engineering design data now lives on a transistor state on some computer somewhere in the world and it's never coming back. We have to go find it.

The Authorship Dilemma

The growing gap between the physical and digital worlds exposes a growing existential threat to construction. Simply put: we can't prove who authored the documents, yet we use them to build high-rise buildings. Offices all over the world throughout the supply chain copy, forward, upload, and attach documents generally trusted as the true copy of the licensed professional's instructions.

We purchase, fabricate, ship, install, commission, inspect, and approve occupancy certificates for bridges, buildings, and roads with nothing more than a dose of trust. We trust that nothing was corrupted from the original instructions along the entire supply chain of decisions.

The Build3 Foundation blockchain solves the proof of authorship dilemma, and we need your help.

Who We Are

We are a member-governed research and development blockchain foundation.

​Our blockchain is designed to function as an authorship-proof layer for the construction industry. This can start as early as feasibility work and extends to the certificate of occupancy. Each certificate of occupancy issued to each building, including the initial build and all subsequent renovations will be tied to it.

These certificates persist as immutable records to serve the public for the life of the building. They offer assurance that the construction performed was done so under the direct supervision and control of a qualified professional. Ultimately, at the end of a building's lifetime, when demolished, the certificates serve as historical artifacts to the land itself.

Build3 Foundation Membership

Would you like to contribute? (no fees). Members may contribute as authors, editors, nominators, and developers. Members also retain voting rights in research and publications.

​You are also invited to if you want to get to know some members.

The build3.foundation has a working prototype of provable authorship engineering supervision. These prototypes show a proof of concept that we can secure the network.

Our position at build3.foundation is that ethics bind the industry to commit to research and participation since we can now secure the network.

How the Industry Can Help

We are not asking for building consulting engineers to become software engineers. There are tons of areas we need help with in terms of publication:

• We would enjoy the chance to work together to collaborate on language for

  • Chapter 1, IBC permitting. This type of modification would help give guidance at the state level.

  • Section 116 (Certificate of Occupancy): with a secure network of proof of authorship, a C of O becomes a multi-signature transfer record.

  • For example, an inspector would prove from a cell phone that the document used for a permit does hash to the signature patterns of the engineer of record and plan reviewer. If it did not, they simply would not have the authorization to issue the certificate.

• : We have ideas for the AIA master contract and master spec.

  • The professionals can use blockchain to manage submittal and shop drawing requirements. We can now prove that some specific party is the author of any particular document. This authorship proof applies to our licenses but also signatures in general during Construction Administration

• more to come...

Blockchain makes it near impossible to make fraudulent engineering judgments with invalid credentials. More on that later. For now, look around at where we are in the documentation. This website serves as a living and breathing documentation of where we are now and where we plan to be.

We will soon release our source code, open-source, and welcome any feedback and new collaborators.

Thank you,

build3.foundation

The National Society of Professional Engineers (NSPE) was established in 1934 to protect engineers and the public from unqualified engineering practitioners.

This process includes strict university accreditation requirements, years of full-time engineering training experience, and two or more examinations.

While not as rigorous as a surgeon's training, it is a long process that requires a minimum of eight years and often longer.

What's the Problem?

So now we have highly educated and experienced super nerds ready to show the world what they can do. So, what's the problem?

Let's talk about NSPE a bit more. From their website, the vision is

...a world where the public can be confident that engineering decisions affecting their lives are made by qualified and ethically accountable professionals.

We love this vision, and we agree. Being an engineer is more than showing off a pocket protector at parties! Every decision made impacts public safety quite often for 20 or more years! And so we agree: qualified and ethically accountable professionals are essential.

NSPE's Core Values

NSPE has a clear and targeted mission reinforced by its published . Those values are

• Ethics and Accountability

• Qualifications

• Professional Advancement

• Unity

Supply / Demand Is Listening

So while NSPE works to help secure the network, it increases the barrier of entry. The problem working against everyone else is: that sometimes it isn't all that hard to get money for a development loan (to the tune of $20T a year).

The unavoidable challenge: rigorous standards and regulations will invariably reduce supply in a regularly high-demand market.

This problem is compounded by the fact we are the are have proven a reluctance toward adopting technologies.

How can we resolve the supply and scalability problem? It is precisely that problem that increases the risk to public welfare even further. How can that enormous demand pushing keep building often, cheap, and fast, be cooled down in a way that meets the professionals where they need to be: concerned with the public welfare?

How can we design a system that will, given those conditions, exhibit transparency to those willing to turn an ethically questionable blind eye?

How can we prove if the seal hasn't been taken and used by someone else fraudulently? How do we ensure the practitioner's competence in making a judgment in a given field?

How it's Handled Now

Long story short: it's not.

Still, governing bodies treat violations as criminal acts. Let's take a look at a few examples:

Texas (1001.552)

§ 1001.552. CRIMINAL PENALTY. (a) A person commits an offense if the person: (1) engages in the practice of engineering without being licensed or exempted from the licensing requirement under this chapter; (2) violates this chapter with respect to the regulation of engineering; (3) presents or attempts to use as the person's own the engineering license or seal of another; or (4) gives false evidence of any kind to the board or a board member in obtaining an engineering license. (b) An offense under this section is a Class A misdemeanor

Indiana (IC 25-31-1-27)

IC 25-31-1-27 Practicing without license and other specific violations

Sec. 27. A person who:

(1) practices or offers to practice engineering without being registered or exempted under the laws of this state;

(2) presents as the person's own the certificate of registration or the seal of another;

(3) gives any false or forged evidence of any kind to the board or to any member of the board in obtaining a certificate of registration;

(4) impersonates any other registrant;

(5) uses an expired, suspended, or revoked certificate of registration; or

(6) otherwise violates this chapter;

Blockchain technology can prove the authorship of digital documents offering a form of digital DNA. This mechanism is helpful and essential in due process for the industry. Continuing to enforce these regulations without blockchain is nearly equivalent to a court dismissing the scientific relevance of DNA in criminal proceedings.

This is the active repository for recently accepted Publication Requests. Research Development is the active playground of the Authorship Team where you are encouraged to watch and engage with the authors about their research.

What you'll find here are the early ideas, sketches, notes, and slow formation of ideas articulating into formal research. The next stop after this phase is conversion to a final technical white paper format. All Research Development projects are subject to Build3 Membership voting approval.

Members are encouraged to comment and offer feedback as these projects develop. If you are not a formal author, you are still a member, and your contribution matters.

There's so much ground to cover, but let's focus on runtime because that's where most of your time: how the runtime works and is constructed.

The runtime is built using FRAME Pallets as a plugin system. Between the Pallets and the Runtime crates, we have been able to create a working prototype of proof of supervision applicable to the construction industry.

Explore our work in progress use cases for build3 if you want a quick look at what is being proposed and how we plan to use the technology.

Once you have a conceptual understanding of runtime and the FRAME pallet system, there are three other important Crates that come with the subtrate_ framework.

work in progress..

Benchmarking can help establish weight for transactions once you study the computational power required to complete them.

The substrate_ team is constantly releasing new pallets and upgrading the existing pallets. Each of them has their own function and are loosely coupled to provide isolated features for the FRAME systems.

Our list includes pallets we are currently using, planning to use, or are researching its use.

frame_system provides low-level types, storage, and functions for your blockchain.

frame_support is like a helper crate. It is a collection of macros, traits, and modules to simplify development of FRAME Pallets.

The frame_executive acts as an orchestration layer for the runtime. It dispatches incoming extrinsic calls to the respective pallets in runtime.

Inspired by this use case with additional reference materials.

An Off-chain worker can be used to process computationally complex transactions with larger bandwidth or data tansmission requirements.

An off-chain worker may be considered as a candidate that can download a large document from IPFS and perform a hash to verify the authenticity of the remote-hosted document.

Students document and inventory public land

Citizen Monitoring and Restoration

Environmental Monitoring (STEAM Project)

NOAA 3D Printed Weather Station

Wildlife Camera

Mite (Landslide, Lahar, Avalanche detection)

work in progress...

Provides a "pot" of funds that can be managed by stakeholders in the system and a structure for making spending proposals from this pot.

Allocates indices for newly created accounts. An index is a short form of an address.

This will allow the runtime to deploy and execute WASM smart contracts.

Federated naming system which allows multiple regisrars to be added from a specified origin.

Registrars can set a fee to provide an identify-verification service.

Anyone can put forth a proposed identity for a fixed deposit and ask for a review by any number of registrars (paying each of their fees).

Registrar judgments are given as an enum, allowing for sophisticated, multi-tier opinions.

substrate_ is taking full advantage of the by implementing the Config object as a trait.

The best practice when building your pallet is to implement .

This will allow you to create all the functionality you want while leaving the concrete types a decision made at runtime.

The Configutation Trait is the way that substrate_ empowers the use of that extensible framework writing.

The Configuration Trait definition is a requirement for all .

frame_system

You'll see this everywhere and wonder why. WHY!? WHAT IS THIS!? The same is true for frame_support but over time they start making sense.

frame_system is the System crate that defines the core types for runtime such as Account ID, Header, Version, Hash, Origin, etc., as well as core

Summary

substrate_ is a Rust-based framework for building blockchains built on the foundation of research.

substrate_ was used to build the .

The Blockchain Data Storage Problem

Storing boolean and integer values is easy. Decimals are a bit more challenging. And strings are extremely limited.

To make things a bit more constrained, ink! contracting language only allows a single low-level primitive, Mapping , for access to contract storage.

This means the front-end developers will have to continuously transform data for most RPC requests.

This is traditionally used for token exchange but could be considered as a starting point to allowing someone to limit the length of time their work is up for review.

Perhaps the claim starts as being offered to a specific preferred reviewer, but then once expired, broadcasts to the network that the offer is now up for grab.

Dispatchable calls are the public endpoints you expose for users so they can interact with your blockchain.

Dispatchable calls must be included on every .

Configuration Trait

Event

IdentificationTuple - Full ID of the validator

OnOffenceHandler - A handler called for every offense report.

Due Date:

Authorship Team:

Author // Phillip Brock

Due Date:

Authorship Team:

Author // Phillip Brock [accepted]

Introduction

offers a solution to the engineering world for a small project which is to provide a two-week turnaround. There are strict rules to follow for that to work on all fronts; one that often catches PermitZIP off guard is allowing a project to kick off before it should.

Authorship Team:

Lead Author // Kenneth Shultz, PE [accepted]

Author // Bradley Edward Layton, PhD PE [pending acceptance]

Editor // Ed Leite [nominated]

Abstract

A common problem articulated for NFTs is that they do nothing to assure ownership. Anyone can claim any digital asset and mint it as an NFT. This research aims to demonstrate the wholly overlooked use for an NFT: authorship.

Example: Shop Drawing Submittal Review

Equipment manufacturers typically author these drawings. If necessary, the trade contractor then marks up the submittal to prepare the document for review. The licensed designer of record then authors their judgment against the submission and sends it back as either approved or denied (resubmission required). At no point in this chain was ownership relevant to the reason for this communication chain.

That process exists to verify compliance with the construction documents. Compliance with construction documents represents compliance with the highly regulated architectural and engineering design process. The highly regulated design process is in place to ensure compliance with the code, and the code's fundamental purpose is to protect public safety and welfare.

Ownership of these documents is entirely irrelevant within this context. Nothing is more important than proof of authorship and compliance with previously authored construction records.

And so we ask ourselves, what is the name for proof of authorship on a blockchain? These authorship proofs belong to a contract. They are nonfungible in that no two authorship proofs can be considered equal. Unlike artwork or music, an authorship-based supervision compliance supply chain is strictly nontransferrable. The signed documents bind to the construction contract immutably, and the construction contract binds in perpetuity to the property.

his module ensures that there is a lock in place preventing the balance to drop below the unvested amount for any reason other than trsnaction fee payment.

The recovery pallet is an M-of-N social recovery tool for users to gain access to their accounts if authentication is lost.

A user is able to make calls on behalf of another account whcih they have recovered.

The recovery process is protected by trusted "friends" whom the original account owner chooses.

A threshold (M) out of N friends are needed to give another account access to the recoverable.

Get and set the on-chain time.

A pallet that allows accounts to give permission to other accounts to dispatch types of calls from their signed origin.

The accounts to which permission is delegated may be required to announce the action that they wish to execute some duration prior to execution happens. In this case, the target account may reject the announcement and in doing so, veto the execution.

membership: build3.foundation

This is the foundation landing page and the place where members can officially join the foundation. This page hosts forums, blogs, membership, and events.

The web page also serves as the main first-time-viewer landing page. A one-pager intended to articulate the mission succinctly.

documentation:

The knowledgebase.

This is an evolving knowledge base of our active work, ideas, and other plans. We use gitbook because it offers developer documentation tools in a super simple way for non-developers to contribute thoughts and ideas.

This is where a lot of preliminary ideas for governance, game theory, use-case applications, technical specifications, tutorials, and other information about the network will be published.

As the ideas grow more and more stable, they would then be converted into the formal white paper documentation for the website or as a stable release for production.

This is where the ideas start to organize and develop into the formal and final technical specifications.

Contributing is easy - just and ask how you can get involved!

governance: build3.dao

Front end for build3 governance. There is no development on this yet, but eventually will be a React-based front-end application rendering the governance features of the build3 foundation.

All our governance work is backend only. If you want to get involved with the front end,

block explorer: build3.x

Front end for build3 transactions. No development here, but the front-end would render whatever features the particular user needs to interact with the blockchain.

All our transactions are backend only. If you want to get involved with the front end,

funding with services:

This just forwards to right now.

The idea behind this domain is to provide a road map for future funding of continued research in areas of blockchain for the industry.

The .com domain would be the home of paid features similar to the relationship between and or MongoDB vs MongoDB's Atlas service.

community:

The home of day-to-day communications about active research projects to spare the inbox.

source code:

Build3 repositories are on GitHub. We haven't made everything public yet - stay tuned!

external:

The framework selected should be secure, permanent, immutable, fast, extensible, modular, and interoperable.

Secure: Rust

The core should be developed in a trusted, secure programming language, called ().

Fast, Extensible, Modular: substrate_

Interoperable: Polkadot

Key strengths in the Polkadot network:

• Building with substrate_ also allows the opportunity to share network security with the in the form of a parachain or parathread.

• Polkadot itself was built with substrate_.

• Both Polkadot

Permanent and Immutable: IPFS

IPFS is a peer-to-peer hypermedia protocol intended to serve as a functionally immutable permanent record.

IPFS (or a similar protocol) would

• allow "proof" that a document was the formal record document and

• that it was signed by a verifiable authority of record.

Qualitative Productivity as a Quantitive Measure

The quality and throughput have never been reliably measured. It works for specific talents and personality types.

What we are talking about is a more true and revealing method of calculating what someone has contributed to their work. This allows for traditionally ignored traits of a worker can be made visible to the network.

The same protocols implemented in the engineering supervision use case also provide a more general-purpose proof of work for all players in the network. Any kind of work can be documented with this protocol.

The Players

There are three humans in this interaction.

• Worker - The person that performs to the standard of care.

• Reviewer - The person that reviews the work against the standard of care.

• Authenticity Validator - The person that affirms both parties acted with good faith.

Staking (Gamifying Quality Control)

Rewards a Function of n Reviews

The review checks the work against the claimed standard of care. If approved on

• Passes First Review: 10 tokens awarded to the worker

• Second Review: 2 tokens awarded to the worker

• Third Review: The total stake is lost and split between the network and burned

• Reviewer is paid 1 token per review

What is ink!?

It's Solidity, but without the chains. Users can build smart contracts to deploy onto your blockchain, but they are also able to be deployed to other networks.

Let's start with a review of the pre-built available by Parity. We'll offer some ideas of how to implement these into the Build3 blockchain to help provide context.

The Collective pallet can be used to generate an instance that represents some group of users with the ability to propose ideas, motion and vote on those proposed ideas.

Configuration Trait

• Origin

Due Date:

Authorship Team:

Author // Omer Bozok [accepted]

What to Expect

This section is dedicated to proposed use-cases with reference to a technical pallet implementation from the framework.

Some are living in the source code, some are only conceptual. Each idea will vary in its development and is expected to grow in depth as contributors work through them.

This allows control of membership of a set of AccountId's.

This pallet stores

• the list of members

• the prime member (master admin account for the membership)

Publication Instructions

How do I Join an Authorship Team?

If you would like to join an Authorship Team (or submit a topic to request an Authorship Team), please (there are no fees), then join our . Once you are on the Discord server, we'll walk you through the process and get to work!

What is an Authorship Team?

An authorship team must contain a minimum of one author and one editor. There may be multiples of either or multiples of both.

Authorship Team

A team nominated and accepted to conduct research for a submitted by a Build3 Member. The Authorship Team must have a minimum of one and one .

Author

The authors are for producing the copy and all supporting documents, sources, images, and graphs. The author is responsible for delivering the research on time to ensure timely delivery of weekly updates to this website, a timely steady-state declaration, and on-time delivery of the final product submitted for approval to the network.

Lead Author

If multiple authors are nominated, one must be titled the Lead Researcher, acting as the project manager. The Lead is ultimately responsible for all duties listed above. The Lead Research received credit for this role in the publication.

Editor

The editor is responsible for quality assurance. The editor reads each iteration of thought, looking for logical fallacies, technical inaccuracies, grammar or spelling issues, confirmation bias, relevance to build3 scope, and other elements to ensure a minimum standard of care for the publication.

The editor is responsible for merging all pull requests from the Author during the Research Development phase.

Publication Request

A Build3 Member-nominated request for publication. If accepted, Build3 lists this topic to the build3.network to help assemble an Authorship Team. Publication requests each have a unique identifier and are numbered in the order they are listed to the network (eg PR1, PR2, etc).

The Publication Process

The path toward publication will move along according to this cycle:

Step 1. Publication Request

A member submits publication requests for consideration into the curated list hosted on this page. Build3 adds approved publication requests to the next available nomination timeslot (each one week in length)

Step 2. Author and Editor Nomination

Build3 Members nominate authors and editors for each publication; self-nomination is permitted (this may change). The foundation lists the publication request for one week, removing it after one week if no author is nominated and accepted. If there are no new publication requests in the queue at the end of the nomination slot, Build3 Members may vote on a previously unsuccessful publication request.

Step 3. Maximum Topics Listed Per Nomination Cycle

Build3 limits the total publication requests to a maximum of 10 for each nomination slot.

Step 4. Research Development

The Build3 Foundation moves all successful proposals to the Active Research page, where the Authorship Team begins Research Development.

1. The Authorship Team must update their progress weekly so that Build3 Members may review and comment.

2. The authorship team is under no obligation to integrate the comments from the community.

3. For the benefit of context for observing Members, the authorship team will respond to all rejected comments with their reasoning.

Step 5. Steady-State

The Authorship Team must declare their work in a Steady-State two or more weeks before the final submission deadline. The Authorship Team will not submit additional significant changes or conclusions for projects announced in Steady-State.

Step 6. Finalizing the Publication

The research team uses the time between steady-state and the deadline to formalize their findings in a technical white paper. The Authorship team submits its work on the pre-determined deadline.

1. Pre-Final Vote: Build3 Members vote to approve or reject the pre-final draft. Approvals and rejection votes may include notes to authors. Authors are under no obligation to address or reply to comments. The Authorship Team determines what changes to incorporate and submits any revisions for the final vote.

   1. Build3 members may nominate dissenting opinions to be included in the addendum of the final publication. Build3 members then vote on the inclusion of those nominated opinions.

   2. When the Authorship Team sponsors a dissenting opinion, it is automatically added to the addendum.

Users of the application need feedback about what happened when they clicked something or interacted on your chain through a public endpoint you've given them.

Transactions can fail for any number of reasons, so your users need to know and that is handled through and Event. Confirmations are similar: tell your user it went okay with an Event.

Right, so my pallet should be able to emit Events?

Yep, pretty much without exception. Here's how:

In the Pallet

type Event

Add Event type to the `Config:

decl_module!

And now add the decl_module! ("declare_module") macro to give access to the deposit_event() method.

decl_event!

decl_event! ("declare event") macro is the way Rust implements an event

In the Runtime

We've defined a trait in the Pallet for Config and so now it has to be implemented at runtime.

In your runtime lib.rs file, add

The code above is simply specifying the type for Event . Note the <T> is not shown and that is because we are defining the concrete type to be implemented by the Pallet we're configuring.

Add the events to the runtime build macro construct_runtime! by adding:

Overview

This page serves to curate the list of research requests and describe the publication workflows. Each item in the list of publication requests is temporarily open to the public for the nomination of Authorship Teams.

To get started

1. Join the as a member (no fees) to participate in authorship or nomination. Only members are authorized to nominate or become and for teams. Members may also submit more topics for consideration.

2. Join the to get in touch with existing members.

This page may be updated occasionally based on community input.

And without further adieu, let's look at the topics open for authorship nomination:

Publication Request List

Publications that do not receive an and nomination are subject to expiry. New proposals will replace expired submissions.

If there are ten or fewer PR's listed below, that means Members can submit publication requests. Reach out on Discord if you have topics for research if the queue is open for ideas!

PR5 | Blockchain Makes Everything Worse for Everyone in Every Industry

Authorship Team:

Author // Ed Leite [awaiting acceptance]

Editor // Kenneth Shultz [accepted]

Getting Setup

The build3 framework is built using the contracts pallet and is compatible with the contract language .

Install the most recent working build.

Separating Block Production and Finality

The build3 chain adopts the concept of separating block production and block finality.

Overview

Manage funds at stake by network maintainers.

This allows a user to voluntarily place funds under deposit. These funds are rewarded under normal operation but are slashed should the staked maintainer be found not to be discharging duties properly.

substrate_ has a long list of pre-packages pallets, but you can also build your own or modify one built by the substrate_ team.

Pallet Structure

A pallet is composed of a few building blocks. These are:

No Std

The first line of code, always. It tells the rust compiler not to use Rust's standard library except when explicitly told so.

This is where crates are imported, especially the substrate_ framework crates.

All pallets will import frame-support and frame-system

Declaration of the Pallet Type

A placeholder to implement traits and methods.

This is used to access features from other pallets, or constants that impact the pallet's behavior.

The Config trait allows you to do the above while keeping Generic Types so you can change define and use something called coin or votes from some other Pallet defined at runtime, but swapped with some other pallet with a runtime update later on.

Have some custom data you want on the chain for users or otherwise?

Runtime Storage is where you do that. You declare storage items you'd like to make accessible to runtime.

Events are how you communicate back to people using the block chain like "transaction confirmed!" or "error! not enough cash!"

This is where you'd build some logic that can be executed regularly in some context, for e.g. on_initialize.

Basically, your blockchain's equivalent to handling webhooks.

These are functions that blockchain users can call. This is often called a Dispatchable Call.

decl_module!

This is the macro where dispatchable calls are composed.

A Little More on Each Topic

Due Date:

Authorship Team:

Author // Ed Leite [accepted]

PR1 | Build3 Roadmap for Blockchain-Based Construction Supervision

Authorship Team:

Licensing Boards and Working Groups

The licensing boards will be constructed from the collective pallet.

We will also introduce a working group technical committee. Working groups define the standard of care for each category of work on the network.