Harbour DAO (HRB) Ethereum base DAO for managing and holding token assets by harnessing the wisdom of the crowd.






  • Harbour is a community-governed, Ethereum-based DAO, Decentralized Autonomous Organization, for managing and holding token assets by harnessing the wisdom of the crowd. All decisions are taken by the users and any generated Ethereum is distributed back to the token holders in a quarterly basis. We are the smartest, safest, and most convenient way to get involved in the blockchain ecosystem.

    Growing potential

    Blockchain is not a concept, it is a reality. It is changing the way we live, work and play. We are only at the beginning stages. The next years will see an incredible amount of growth in this space as we go further along in this collective journey. There is no doubt surrounding the overall growth potential of this market. Some will win and some will lose, but with Harbour, you are on the best possible ship to find your way to value, and to weather any storm.

    Components of Harbour DAO

    In order to create the Harbour DAO, several components are required, which comprise the
    essence of the DAO. Therefore, we are highly devoted to making them work harmoniously
    together.


    ● The System: The system is made up of a combination of smart contracts on the
    Ethereum blockchain. These smart contracts contain all the logic required to make
    Harbour work.

    ● The Platform: The platform UI will offer an easy way for our community to interact with
    the system using their browsers.

    ● The Harbour Token (HRB): The Harbour Token gives holders the right to vote on
    proposals as well as access to some of the surplus ETH that Harbour generates.

    ● The Community: Without a strong and thriving community Harbour will never function,
    the one true value that Harbour has is the people interacting with the system. Harbour is
    not made for the individual, it is created for the whole. As individuals in this ecosystem
    we are powerless, however Harbour gives a community the strength through its
    combined wisdom to create value.
    The Harbour team is focused extensively on creating a strong community, as the success of the
    DAO depends on an engaged network of participants. Additionally, Harbour will only have
    achieved its goal when the team behind the product is no longer needed. Harbour is
    distinguished from other DAOs in its promise of true autonomy. As such, Harbour’s creators are
    determined to step down from their guiding positions.




    The Harbour DAO system consists of a large network of smart contracts. The full technical
    specification of these contracts can be found here. The smart contracts can be categorized into
    groups that make up larger modules in our system. The most important parts or modules of the
    system will be summarized in this document.



    The Congress


    At the heart of Harbour is the congress, which it controls the Harbour Wallet and is responsible
    for executing proposals. When token holders create proposals they do this through the
    congress, through which all interactions between a holder and Harbour occur. Additionally all
    communications between different parts of Harbour are usually delegated through the congress.
    The congress has been split up into multiple contracts in order to allow for easy updating and
    testing.


    Proposals

    There are various types of proposals that can be voted on and executed. Proposals are the
    mechanism by which holders participate in decision making. There are multiple proposal types,
    which each serve a different purpose and involve distinct usage.
    The currently defined proposal types are as follows:

    1. ICO Contribution: This is one of the core proposal types. It is used to diversify into
    different ICOs. This proposal has yes or no options. Additionally, when holders vote yes
    they can pick from a range of percentages for how much of Harbour’s holdings they
    would like to contribute.

    2. DAO Change: This along with ICO Contribution proposals is another fundamental part
    of the project. This proposal type provides token holders with the ability to 100% change
    every aspect of the DAO. These proposals execute automatically and work by changing
    configuration values on the DAO, such as Dividend rates, Proposal Creation costs etc.

    3. Buy Proposal: This proposal allows token holders to vote on contributing to an existing
    Token. This functionality will work automatically through the usage of various exchanges.
    Holders will have the option to vote from a range of 2-10% in increments of 2% for how
    much ETH they think Harbour should use to buy more tokens.

    4. Sell Proposal: This proposal allows token holders to vote on selling a token the DAO
    currently holds. It is planned that this functionality also works fully automatically by using

    decentralized as well as centralized exchanges. Holders will be able to vote from a range of 10-100% in increments of 10% for how many tokens they think Harbour should sell.

    In order to reduce spam when creating proposals, there will be a fixed ETH fee associated with
    creating a proposal. If a proposal passes successfully, the creator will have the fee reimbursed.
    We believe this not only stops spammers from creating fake proposals, but also motivates token
    holders to make good proposals they think will pass.


    Exchanges

    One challenge Harbour faces is interacting with exchanges. Although there are various decentralized exchanges, many of these do not have enough volume. For this reason, the Harbour developers have come up with a way to interact with both centralized and decentralized exchanges using smart contracts. One of the issues Harbour faces, is the volumes of tokens it will potentially hold. This can lead to various issues when trying to offload some of these tokens on exchanges, to convert them back into ETH. For this reason a smart contract will be implemented, which will provide Harbour with a way of splitting the funds that token holders want to sell amongst various exchanges. The mechanism will be fed data from multiple oracles, including things like volume and price. These data points are relevant that Harbour does not create huge sell walls when listing tokens on exchanges. Not only is this crucial for Harbour itself, but it is also important for exchanges as Harbour would otherwise have huge potential in manipulating markets simply by selling off holdings. All trades that happened on exchanges will be stored in a database, this will include the transactions that occurred, the volumes sold and at what price. This will be implemented for both centralized and decentralized exchanges.

    Adfero 

    A project that was spawned out of Harbour, Adfero is a system that utilizes smart contracts to contribute to ICOs as soon as they open. It also holds an index of all known ICOs that can be contributed by users, this index contains information that can be submitted by various users and verified by the community. Additionally it allows users to rate ICOs on their legitimacy. The system is fully decentralized and will also be made available to users who do not hold Harbour tokens.

    Token Distribution

    The ICO will start on July 15th and will last until July 29th. A maximum of 650,000 HRB Tokens
    will be created during the ICO and no more will be created thereafter. Participants must submit
    their contributions from an address from which they hold the private key to the address that will
    be specified our website prior to ICO begin. HRB tokens will be created every time ETH is
    contributed to the crowdsale, no more than 500,000 HRB will be created for contributors during
    the crowdsale. To mitigate the effect of large actors, there will be a 5,000 ETH contribution cap
    per address. Optimal gas pricing conventions will be released prior to the ICO.


    Token Allocations









    A maximum of 650,000 tokens will be created 500,000 of which will be available to contributors during the ICO. After creation of these original tokens no more will be created thereafter. For the further development of Harbour tokens will be allocated, this will be an additional 10% of however much was raised. An additional 20% will be created and then distributed among the founders. Half of the founder tokens however will be locked for a year however. Once all the extra tokens have been created, founding team together will own 15.4% of the total supply, meaning every founder owns 3.85% of the total supply, and the development fund will comprise of 7.7%.

    The founders will not receive any further compensation, for this reason the current value was agreed upon. As the development of the project will be done for free from the founders side.

    Harbour DAO Roadmap:

    • January 2017

      Harbour was envisioned

    • April 2017

      Development started

    • July 2017

      Initial Coin Offering

    • Q4 2017

      First release on testnet

    • Q1 2018

      Release Harbour V1

    • Q4 2018

      Harbour goes fully autonomous

    The Founding Team

    ...

    Dean Eigenmann

    Co-Founder & CEO

    ...

    Dylan Dewdney

    Co-Founder & CSO

    ...

    Nick Jorens

    Co-founder & CIO

    ...

    Klajdi Ciraku

    Co-founder & COO

    Advisors

    Meet the people who make sure Harbour can exist!

    ...

    Douglas Tarabini

    Senior Branding & Marketing Advisor

    ...

    Addison Cameron-Huff

    Senior Legal

    Links:

    Website:

    Blog:

    Slack:

    Twitter:

    Reddit:

    Github:



  • Harbour DAO (HRB) Technical Specification


    Architectural layout


    1. Congress: At the heart of Harbour is the congress, it has control over the Harbour
    Token Wallet as well as executing different proposals. The way it functions is dependent
    on the DAO Configuration.

    2. Harbour Token Wallet: The Harbour Token wallet is a smart contract that stores ETH
    as well as other ERC20 tokens, however this contract can be updated 1 to additionally
    support other types of tokens such as those conforming to the ERC2232 standard. The
    congress is the exclusive owner of the wallet at time when Harbour goes completely
    autonomous, and no other outside system will be able to withdraw funds . However
    the multisig3 backdoor will still exist for emergency situations. The congress is
    responsible for withdrawing funds to Adfero (to participate in ICOs) and the exchanges
    (to change the token composition of Harbour).

    3. DAO Configuration: The DAO configuration is a smart contract that is used to store
    different attributes of the congress, this can include things such as what the minimum
    voter quorum is, or the cost of a submitting a proposal. The DAO configuration can be
    changed through proposals. The reason this smart contract has been created, is for
    simple segregation of concerns.
    1 https://github.com/ethereum/EI...
    2 https://github.com/ethereum/EI...
    3 https://github.com/ConsenSys/M...

    4. Proposals: There are various types of proposals that can be voted upon and executed,
    in the deepest sense they are how a holder participates in Harbour. The Proposals are
    created through the congress by token holders. The congress is also responsible for
    executing these proposals.

    5. Exchange: The exchange system is an interface that connects Harbour to centralized as
    well as decentralized exchanges. The interface was created to be able to easily buy and
    sell tokens across various platforms, while communicating with a single smart contract.

    6. Adfero: A project that was spawned out of Harbour, Adfero is a system that utilizes
    smart contracts to contribute to ICOs as soon as they open. It also holds an index of all
    known ICOs that can be contributed by users. The list contains ratings that are submitted
    by various users and verified by the community. The system is fully decentralized and
    will also be made available to users who do not hold Harbour tokens.
    This is a rough overview of how the DAO will look technically, however there are certain
    additional smart contracts that have not been displayed here. These include things like how the
    excess ETH will be distributed among holders. The reason why some of these smart contracts
    and aspects have not been listed here is due to the fact that their exact implementation is not
    yet fully decided on. We are currently going through multiple iterations in order to find the most
    viable option. Additionally we have also excluded temporary wallets from this diagram due to
    their complexity, and them being a wall between the Harbour token wallet and the exchanges.
    The congress contract will be provided through a proxy , this is due to the fact 4 that we may need
    to be able to update the congress. As solidity does not natively support such a feature, a smart
    contract will need to be implemented that solves this issue for Harbour.

    Interactions




    The above diagram displays the interactions that occur within the DAO. Although it may seem
    complex, the diagram illustrates a system that has been kept rather simple. Through the
    separation of concerns, like splitting the execution of proposals out of the congress the smart
    contracts are able to be kept simpler. Not only do we want to keep our smart contracts as simple
    as possible, but also the interactions between them.
    The interaction specification is currently a design, changes may occur to this definition in order
    to improve the system. The current specification also makes the code far more simple to audit
    and test, as logic is split up into small chunks that are easy to comprehend and unit test. Along
    with unit tests, various integration tests will also be written to validate the entire functionality of
    the DAO.

    The Congress

    The single most important aspect of Harbour is the congress. It is the brain as well as the heart
    of the DAO. While most DAOs have a simple proposal system with the option for token holders
    to be able to either vote in favour or against, Harbour requires something a little more modular.
    Another aspect that differentiates Harbour from similar projects is the aimed goal of full
    self-governance. Unlike other DAOs, holders of the Harbour token will be able to change the
    DAO in every aspect.

    Proposals

    In order fo Harbour to achieve full autonomy, holders need to have the ability to create a variety
    of proposals. Currently it is planned for the congress to have multiple proposal type definitions.
    In the future these proposal structures could be merged into one. However there are currently
    limitations and technical challenges that need to be overcome before this can happen.
    The current proposal types that are planned are as follows:

    1. ICO Contribution: This is one of the core proposal types. It is used to diversify assets
    into different ICOs. This proposal has yes or no options but in addition, when a holder
    votes yes they can also pick from a range of percentages for how much of Harbours
    holdings they would like to contribute.
    One of the issues that needs to be addressed is, if the popular percentage is shared by
    multiple options. Our current solution is that if we ever encounter such a draw, we will be
    holding a revote.

    2. DAO Change: This along with ICO Contribution proposals is another fundamental part
    of the project. This gives token holders the ability to 100% change every aspect of the
    DAO. These proposals execute automatically, and work by changing configuration
    values on the DAO. Such as Dividend rates, Proposal Creation costs etc.

    3. Buy Proposal: This proposal allows token holders to vote on contributing to an existing
    Token. This functionality will work automatically through the usage of various exchanges.
    Holders will have the option to vote from a range of 2-10% in increments of 2% for how
    much ETH they think Harbour should use to buy more tokens.

    4. Sell Proposal: This proposal allows token holders to vote on selling a token the DAO
    currently holds. It is planned that this functionality also works fully automatically by using
    decentralized as well as centralized exchanges. Holders will be able to vote from a range
    of 10-100% in increments of 10% for how many tokens they think Harbour should sell.

    Range vs 2 options

    The range voting option system discussed for the ICO Contribution proposals will also be
    applied to Buy and Sell proposals .
    The range vote is an extension of the regular yes/no vote. It gives voters the opportunity to
    specify a certain percentage along with a yes vote.
    This works as follows:
    51% voted yes
    - 25% voted for a 10% purchase
    - 12.5% voted for a 20% purchase
    - 12.5% voted for a 30% purchase
    49% voted no
    It is clear that this vote will pass, due to the fact that 51% voted yes. This causes the votes to be
    further evaluated to select percentage with the most votes. In the above example we see that a
    10% purchase is the clear winner, as 25% of yes voters selected that percentage range.



    Execution of proposals

    In order to keep the initial congress smart contract as lightweight as possible we require a
    method that allows us to execute proposals and run certain checks. These areas of the
    congress should be easy to update without having to re-release the entire congress.
    To do this each proposal type has a proposal executor, these executors are referenced in the
    congress smart contract. This system gives us the ability to update execution logic without
    having to deploy our entire DAO again. To do this we simple release a new executor, update the
    congress reference and delete the old executor.


    The above image shows the sequence of how a proposal is executed through the executors.
    The congress validates that the proposal has passed through the proposals specific methods.
    Once it can validate that it has been passed, the congress triggers the executor for the specific
    proposal, there are different executors for the various proposal types. The executor then runs
    the logic required to execute a proposal and confirms that the execution was successful. Once
    the congress receives this execution it can mark the proposal as executed. This will close the
    proposal and prevent it from ever being executed again.
    The executors will be mapped to their proposal type in the congress smart contract, with this
    method we can also very simply add new proposal types by creating a new proposal factory and
    adding a new executor. The same way we can easily add new proposals, this system also
    enables us to easily remove old proposal types that we no longer require.

    DAO Changes

    Initially certain aspects of the DAO will not be changeable, however throughout the development
    of Harbour the developers will slowly roll out more changeable aspects of the DAO. The reason
    why we have decided to not allow everything to be changed up front, is due to the fact that
    certain aspects are required to stay the same throughout development. Such as the reserve






    Making the DAO changeable, is technically speaking quite simple. This was done by exporting
    all of the configuration values we have in the DAO into a separate smart contract. This is the
    DAO configuration. Through the configurations permission management, the Harbour team can
    define which keys can and can’t be changed. These powers will be revoked as soon as the
    Foundation takes a community level role, at that point only the Congress will be able to make
    any modification to the DAO configuration.






    Exchanging

    Exchanging requires a lot of complexity, this is due to the fact that we require both buying and
    selling of tokens. For this reason, the system will be supported through Javascript code, this
    code will interact with our smart contracts using the web3 interface. Proposals 5 that have
    passed will be handled by an executor like any other, this executor however will trigger multiple
    exchange interfaces including those on the blockchain and those off-chain.
    For transparency we are working on keeping as much of the exchanging logic within our smart
    contract, we are focused on ensuring only minimal functions are carried out by the Javascript
    code.






    ICO Contributions

    Due to the various types of ICO contracts, the contribution system requires a little more
    complexity to build. In order to keep Harbour relatively simple we have decided to migrate this
    code into a new project called Adfero. Once a proposal has passed, the executor will send
    funds from the Harbour wallet to the Adfero smart contract, the rest of the contribution logic is
    then implemented in Adfero.


    Delegates

    The Congress will implement a basic delegate system, this will allow less informed and less
    active token holders to delegate their votes to token holders they deem as more fit. In order to
    keep it a fair and transparent system, we have come up with a method to keep delegate votes
    fully transparent. Delegates will need to finalize their vote before they are allowed to officially
    vote on the proposal. A delegate is not permitted to change his vote from his original intention

    Combatting Spam

    • Fee

    In order to reduce spam when creating proposals, there will be a fixed ETH fee associated with
    creating a proposal. If a proposal passes successfully, the creator will have the fee reimbursed.
    We believe this not only stops spammers from creating fake proposals, but also motivates token
    holders to make good proposals they think will pass.

    • Time Cooldown

    Along with this fee, there will also be a limit placed on the amount of proposals a single user can
    generate within 24 hours. The time cooldown period has not yet been decided upon, however
    this too will be one of the attributes that can be modified in the DAO.


    • Combatting Fraud

    In order to combat fraud, and stop big holders from being able to influence the entire DAO, we
    have decided that proposal creators will only be able to vote on their proposal with a limited
    amount of votes. There is also a minimum voter quorum which will most likely be around
    10-20% of all tokens.
    Additionally, it is currently in discussion if votes should be capped to a certain percentage.
    Meaning that a user with 50% of all tokens for example can only vote with around 10%. How
    this mechanism is fully laid out has not been totally established. However we are working daily
    to figure out these pressing issues, and we look forward to community involvement and input.


    Profit Distribution

    One important aspect of Harbour is the goal to distribute its profit. This will happen on a
    quarterly basis, and the distributed amount will be dynamically adjusted by the DAO. The
    distribution will be based on the amount of revenues converted back to ETH in a given quarter.

    A certain percentage will be subtracted from the returns, to reinvest in the DAO. With the aim of
    increasing the value and holdings of the subsequent DAO. It is currently set at 25%, however
    this value too is dynamic and can be changed through DAO Change proposals .

    Harbour Token Wallet

    The Harbour Token wallet is a smart contract developed for storing the tokens held by Harbour.
    Current implementation proposals involve a splittable wallet, the benefits of this would mean
    that not all assets are held in a single smart contract. This considered implementation would
    look like this:

    The viability of the above displayed implementation is still under discussion. However we are
    certain that the implementation we decide to go with in the end, will set a new standard for how
    DAOs hold their funds.
    The security and safekeeping of tokens held by Harbour is of utmost importance, for this reason
    there are currently multiple systems which are in consideration for implementation. These are all
    being analyzed on their viability and security.
    Our current design mixes multisig wallets with another system that we have specifically
    designed for this use case. Our wallet will require proposal information to be passed when a
    transaction is requested, the wallet will analyze the proposal and ensure it has passed.
    Transactions from the congress will not be executed unless the Harbour wallet validated that a
    proposal has passed successfully. However in case all funds need to be withdrawn from the
    wallet, a multisig system will be implemented where in case of an emergency transactions can
    be executed to withdraw the funds into a new wallet.

    This system however has its limitations, for buy and sell proposals we can only have one
    transaction, but we may need more when interacting with multiple exchanges. To solve this
    problem, we have come up with temporary wallets. These are smart contracts the congress will
    deploy whenever an exchange based proposal has passed. The congress will then trigger a
    transfer from the harbour wallet to this temporary wallet which can then be used by our
    exchange interface.








    1) Congress triggers a transaction from the Harbour wallet to create a new temporary
    wallet.
    2) Harbour wallet transfers requested tokens to the new temporary wallet.
    3) Congress triggers the exchange with address of the temporary wallet.
    4) Exchange uses funds in the temporary wallet and exchanges them.
    5) Exchange transfers the result of exchanging tokens back into the harbour wallet.
    The exchange in the above diagram represents our entire exchange system, which will be
    wrapped by a single interface for simple usage in smart contracts.



    Exchanges

    One challenge Harbour faces is interacting with exchanges. Although there are various
    decentralized exchanges, many of these do not have enough volume. For this reason, the
    Harbour developers have come up with a way to interact with both centralized and decentralized
    exchanges using smart contracts.









    The Web3 wrapper can trigger the DAO to transfer funds to the exchanges, in order to protect
    this system, we will implement an authentication system. With the proposed addition of State
    Channels on the blockchain, this system could be massively simplified by implementing one.
    This is to ensure that hackers cannot funnel funds into a private account.








    Mechanism

    One of the issues Harbour faces, is the volumes of tokens it will potentially hold. This can lead
    to various issues when trying to offload some of these tokens on exchanges, to convert them
    back into ETH. For this reason a smart contract will be implemented, which will provide Harbour
    with a way of splitting the funds that token holders want to sell amongst various exchanges. The
    mechanism will be fed data from multiple oracles, including things like volume and price. These
    data points are relevant that Harbour does not create huge sell walls when listing tokens on
    exchanges. Not only is this crucial for Harbour itself, but it is also important for exchanges as
    Harbour would otherwise have huge potential in manipulating markets simply by selling off
    holdings.

    Centralized

    Centralized exchanges will be interacted with using our web3 wrapper. This means that our
    smart contract will trigger events that are handled in Javascript. Those events then call different
    functions using various exchange APIs. All transactions and logs that happen between the
    wrapper, exchanges and smart contracts will be stored in a database and made fully public.
    This is to promote transparency and ensure that there was no wrongdoing in the process. The
    audit logs will be available through the Harbour website.


    Decentralized

    Decentralized exchanges require a similar approach to centralized exchanges. At the time of
    writing we are looking into using the 0x protocol for interacting with decentralized 6 exchanges
    and exchanging ERC20 tokens. The main advantage here is that there will be no need for a
    centralized database. The protocol will allow anyone to view/audit the actions undertaken.

    Auditing

    Our audit is a set of monitoring tools that allows any person to easily validate actions taken and
    portfolio balances. All of this will be viewable through a web interface and via API’s.
    For each exchange account that is going to be used for trading on the exchanges, we will create
    a view-only API key that will allow anyone to verify the balance and trade history of the account.
    Harbour will be hosting an audit page with a full list of API keys and aggregate account
    information, automatically pulled from the exchanges by our service.
    For convenience sake we will also dedicate a section on the platform to the aggregation of all
    the available information, ranging from trade history to events our contracts broadcasts, visible
    for everyone to see. This will allow non technical inclined users to easily understand all the
    information whilst more technical people can check everything in detail using the API keys the
    exchanges provide.






    Adfero

    Adfero describes a system for trusted ICO information, it facilitates a simple method to verify
    and rate various ICOs. Adfero is composed out of an index and an ICO contribution
    management system. Both of which are vital aspects for the Harbour project.
    The ICO contribution system allows people to easily contribute into an ICO with a single
    transaction. This means that we can reduce the amount of transactions happening on the
    ethereum network. Potentially this system could reduce a lot of the problems we have seen with
    recent ICOs drastically.

    The Index

    The Adfero index strives to create one of the most comprehensive lists of ICOs on the ethereum
    network, it will be powered by smart contracts and will utilize the power of the blockchain
    community to submit and validate information.
    Not only will users be able to vote on the validity of information submitted for a specific ICO,
    creating a cryptographic certificate for all data submitted. They will also be able to vote on the
    ICO itself, for example if they believe it is fraudulent. There will be a reputation based system for
    this entire process, meaning that long time contributors votes will have more power than those
    of new contributors on the platform.


    ICO Contributions

    The above diagram shows the basic interactions between various parts of Adfero, the ICO contribution contract being the central part of the entire system. It withdraws funds to send to the ICO and reads various ICO information to understand how funds must be contributed.






    The ICO contribution system is built pretty simple, for every ICO a contribution wallet will be
    generated, users deposit funds into this wallet and they will be used when contributing to the
    ICO. Currently we are still discussing if we will create a wallet per ICO or will be able to split a
    single wallet into multiple ICO wallets, the currently most viable seeming is the latter.


    Every ICO will be managed in the ICO contribution contract, for every ICO a set of rules will be
    definable, this includes the things like:
    1) Method required to be called on the ICO contract
    2) Maximum gas price
    3) Maximum contribution per address
    These rules will be stored in an ICO information contract, they will also be made viewable
    through the index, this is where the 2 aspects of Adfero overlap.
    The defined rules will be taken into consideration by the contribution system, for example our
    wallet will not accept more ETH than the maximum contribution. The method that is required to
    be called by the ICO contract will be stored as transaction bytes already, this is so that the
    transactions can happen automatically without requiring additional information before execution.
    Finally to contribute, the contract will need to be manually executed, this will be done by any
    community member using Adfero. We will offer a bounty to any user who manages to execute
    the contract successfully in order to incentivize them. Currently we are also experimenting with
    doing this automatically using Javascript code, however if that code fails we will most likely still
    stick to the bounty system to ensure that ICOs are contributed to.







  • Very Good!



Looks like your connection to Cryptocentral was lost, please wait while we try to reconnect.