dock.io

dock.io is a decentralized data exchange protocol that lets people connect their profiles, reputations and experiences across the web with privacy and security.

About dock.io

The dock.io protocol is a decentralized data exchange protocol, intended to incentivize the exchange of shareable personal data, with a focus on professional information such as work experience, connections, and reviews. Dock.io is poised to disrupt the space of centralized professional networks such as LinkedIn, Upwork, or Glassdoor, and the fragmented user experience they provide, by enabling users to have control over their data and share it easily across applications, without being bound to any particular platform. Using the dock.io app, users will input signed and verified content and choose where it, as well as data received from other platforms in their name, is shared. Applications will be required to pay other applications with tokens in order to access their user based data. Only applications, not users, will be monetarily incentivized to share data; users will benefit from having control over their data. Dock.io is developed by Remote.com, a platform that connects professionals with remote and freelance jobs using artificial intelligence, with over 2 million users. Integration of dock.io with Remote.com (as well as additional unspecified partners) is planned for Q2-2018.

Token Sale Use of Blockchain

Product

3.6
Product
Readiness

Is the product ready for use? Is there a working prototype or MVP? How long until it is operational?

3.0
N/A
3 - Prototype / MVP / alpha.
Appeal

How appealing is the product? How good or necessary is it? Does it have a distinct edge?

4.0
N/A
4 - Captivating.
Target User Base

Is it mass market or niche?

3.0
N/A
3 - Has growth potential.
Competition

Are there many other similar solutions or is this one of just a few, or even one of a kind?

4.0
N/A
4 - Few competitors / a leading solution.
Innovation

How innovative or inventive is the product, either conceptually or technologically?

4.0
N/A
4 - Original, specialized.

Product

  • Dock.io makes it possible for users to transfer any type of information between apps or platforms and keep their information up to date everywhere. The dock.io app will serve as a connector between apps in the ecosystem, allowing users to manage their information and preferences regarding how information is shared or synced. The app is currently in alpha.
  • The dock.io protocol makes it possible for a third party application to receive push updates from a user about activity on another application, and send back its own updated state. It also makes it possible for third party applications to use business application data (task management, collaboration, file sharing) to assess individual work history and performance, and to create reputation scores, network centrality scores, performance reviews, or even vouch for whether an individual works at a specific company.
  • In dock.io, tokens will be used to incentivize applications to share their data rather than hoard it. Tokens will not be used to incentivize users to share data with applications. When a user sends data from one application to another, the requesting application will pay a fee for access to the data (first to the delivering application, then to be burned). Users will not have any monetary incentive to interact with the product or their data; their benefit will come from having control over their data. The company does currently reward users for inviting friends to the network, to help with early network growth, and plans to continue such efforts until a substantial user base is reached. App fee structures are not discussed. There are no platform fees or rent extraction; the company is funded solely via the token sale.
  • Notable dangers of the model, stated explicitly in the whitepaper, are with regard to applications monopolizing user data or or sharing it without approval, thus effectively undermining the users’ control over their own data, but the model is designed to disincentivize such behavior.

Product Whitepaper

Use of Blockchain

4.2
Use of Blockchain
Blockchain Development

Is blockchain technology essential? Does it make the solution significantly different and better?

4.0
N/A
4 - Innovative use of blockchain technology.
Disruptive Blockchain Advantage

How disruptive is the introduction of blockchain technology into the product's market space?

4.0
N/A
4 - Generally disruptive.
Need for a Custom Token (vs. BTC or ETH)

Is the token essential or could it be done just as well or better with fiat or Bitcoin?

5.0
N/A
5 - Real, tangible, utility-based value.
System Decentralization (besides token)

How decentralized is the system architecture other than the token (e.g., data collection, storage, access, and use, or decision making processes, etc.)?

4.0
N/A
4 - Mostly decentralized.
Contribution to Blockchain Ecosystem

How compelling is the solution's contribution to the evolution of blockchain infrastructure and economy?

4.0
N/A
4 - Captivating.

Use of Blockchain

  • The dock.io app serves as a connector between apps in the ecosystem. Token costs, as well as any exit fees, will be denominated in Fiat, and a centralized oracle will provide live exchange rates to the dock.io smart contract.
  • Tokens will be used to incentivize applications, not users, to share data. Users will have no monetary incentive, but will benefit from having control over their data.
  • Dock.io utilizes the IPLD2 specification developed for IPFS to perform content addressable data exchange. The unencrypted delta’s of the data format updates are hashed, versioned, and anchored to the Ethereum blockchain using a modified specification of the Chainpoint open standard. This provides data integrity, making it possible for applications to verify the validity of data format updates without exposing the data itself. By encrypting the updates to the different applications’ public keys, the user remains in full control of who receives push updates. (Also, any account can sign the on-chain data format version hashes of any other account, and applications may require the signatures of certain other applications for verification.) Users can also choose to publish unencrypted updates and data to IPFS directly, so as to make them freely accessible. All versioning of the data formats will happen client-side and off-chain. The first implementation will use simple GIT4; the end-goal is a versioned key-value store similar to Noms5.
  • Dock.io data formats are essentially “the equivalent of microformats for Ethereum smart contracts”.

Use of Blockchain Roadmap

Whitepaper

3.8
Whitepaper
Comprehensiveness

Does it cover the full scope of the problem and solution?

4.0
N/A
4 - Satisfactory coverage, well written.
Readability

Is it easy enough to understand?

4.0
N/A
4 - Easy to read and understand.
Transparency

Does it candidly describe and disclose where the project now stands, how much exists and how much still needs to be done, etc.?

4.0
N/A
4 - Informative disclosure.
Business Plan Presentation

Does it contain a viable, comprehensive business plan?

3.0
N/A
3 - More information required.
Technology Presentation

Does it present a well thought out technological architecture? Does it address implementational challenges?

4.0
N/A
4 - Clear, well thought out, realistic.

Whitepaper

  • Whitepaper is concise yet detailed, and presents a coherent business model and technical solution overall, but not a concrete development timeline. An unrevealing roadmap is provided elsewhere (on Medium). Whitepaper candidly discloses and explains underlying risks and complexities.
  • Some aspects of the model are still a bit unclear or difficult to understand, and perhaps should be explained better, particularly the token economics, but it appears that quite a bit of thought has gone into creating a token model that supports a truly distributed data economy.

Whitepaper Compliance

Roadmap

3.8
Roadmap
Concreteness

Is there a concrete and practical development plan (vs. just a conceptual vision)?

3.0
N/A
3 - An overall plan, major milestones stated.
Feasibility

Is the development plan realistic? Is it based on reasonable goals and timelines?

4.0
N/A
4 - Realistic.
Vision

Is there a larger, long-term vision?

4.0
N/A
4 - Long term.
Dependencies (services or capabilities)

How available, operational, or trusted are the other systems or capabilities on which the project relies?

4.0
N/A
4 - Available and trusted.
Current Position

Where is the project now, relative to its vision and plans?

4.0
N/A
4 - Past a few hurdles.

Roadmap

The currently available roadmap lists the following:

  • Jan 2018: Release of the dock.io app (currently in alpha) and Rewards program.
  • Q1 2018: Partnership announcements (currently Remote.com, FundRequest, and SmartRecruiters are mentioned on the website) and Token Sale.
  • Q2 2018: Remote.com Partner Integration followed by additional partner integrations.
  • Q4 2018: Network Data Exchange – applications will be able to exchange data via DOCK tokens with encrypted packages over the IPFS network.

Roadmap Company and Team

Compliance

3.8
Compliance
Token Utility (value through usage)

How much use is there for the token itself (regardless of its value as an investment vehicle)?

3.0
N/A
3 - Limited or uncertain use cases.
Token as Security (tradable instrument)

How valuable is the token as an investment vehicle or financial instrument?

4.0
N/A
4 - Not as such, or compliance is assured.
Token/Smart-Contract Readiness

Is the blockchain infrastructure of the project ready for use? Is there a working prototype or MVP? How long until it is operational?

3.0
N/A
3 - Prototype / MVP / alpha.
Attention to Compliance Issues

How much attention is given to compliance (via token and ecosystem design, token sale participation, etc.)? Is this issue addressed directly and coherently?

5.0
N/A
5 - Professional, audited.
Legal Review/Risk Assessment

What kind of legal documentation (reviews or agreements) and risk assessment are provided?

4.0
N/A
4 - Professional.

Compliance

Generally, the DOCK token provides applications with access to other applications’ user based data. Applications which are also token holders can signal on their contracts which data formats they accept via a simple list with data format names. DOCK token holders also gain voting rights, allowing them to introduce new proposals and vote on the future development roadmap of the protocol, but the mechanism by which this happens (submission and voting process, governance structure, fund allocation, etc.) is yet to be clarified. Token supply is deflationary via burn mechanism.

The company is working with Deloitte, a big four accounting firm, to ensure it is optimally managing funds, as well as with two top US law firms to ensure it is doing everything it can to be compliant. SAFTs are used for presale investors, as well as KYC for every investor, and a few regions are prevented from participating. At the time of token distribution, the network will be live with the full voting utility.

Compliance Token Sale

Company and Team

3.8
Company and Team
Company Stage and Foundation

Is the company already established? Has it raised funds before? Is it mature?

4.0
N/A
4 - Established with some fundraising history.
Background of Lead Team Members

Do we know who they are? Do they have LinkedIn profiles? Do they have solid, relevant backgrounds?

4.0
N/A
4 - Verifiable relevant experience.
Team Assembly and Commitment

Is a solid, fully committed core team in place? Do they have online (e.g. LinkedIn) profiles showing sufficient relevant experience? Is their participation transparent?

4.0
N/A
4 - Fully assembled and committed.
Team Skill Set Relevance

Does the amount of talent and skill in each area seem to fit the project requirements?

3.0
N/A
3 - Correlated to project requirements.
Team Skill Set Balance

Is the team well-rounded (biz/tech/blockchain)? Is there sufficient talent and skill in all areas of required development?

4.0
N/A
4 - Good, sufficient for each aspect.

Company and Team

California based Remote.com (the developer and primary integration partner of dock.io) was founded in 2017 and claims over 2 million users.

Cofounder and CEO Nick Macario was previously founder and CEO of branded.me, a professional platform which grew to 3 million+ members and was acquired in Nov 2016 by Outsource.com, a secure marketplace focused on delivering high-quality projects to freelancers. Cofounder and COO Elina Cadouri is also co-founder of Outsource.com. Ten additional team members, mainly developers, are listed, all with active LinkedIn profiles (Remote.com has 35 employees on LinkedIn). Lead Blockchain Engineer Evgeniy Zabolotniy does not list blockchain experience; was Chief Architect at branded.me. Piotr Swies is a Senior Engineer at Remote.com and a Blockchain Engineer at dock.io, “skilled in designing and implementing distributed systems with microservices architecture”.

Company and Team Product

Token Sale

3.8
Token Sale
Raise Amount Max

Is there a clear cap? Is the maximum raise amount modestly sufficient (as opposed to either greedy or insufficient)?

4.0
N/A
4 - Well suited to needs and plans.
Raise Amount Min

Is the minimum raise reasonable considering the development plan? Are there raise-amount dependent milestones?

4.0
N/A
4 - Reasonable, sensible.
Fund Allocation

Is fund distribution and allocation reasonable and justified?

4.0
N/A
4 - Well defined and reasonable.
Token Allocation

Is the ratio of tokens sold to those kept reasonable? Does it prevent the company from having too much control?

3.0
N/A
3 - Sufficient company/community interest balance.
Media Presence and Following

Is the sale being talked about in Reddit, Bitcointalk, Social Media, Medium, etc.? Is information available and accessible? Is there interest?

4.0
N/A
4 - Solid exposure and interest, good impression.

Token Sale

  • Total Supply: 1 Billion tokens
  • Token Price: $0.07
  • Hard Cap: $20M USD (includes both private pre-sale and public sale). The company has already raised $12M through the presale and has a very high likelihood of reaching the $20M target.
  • Token Distribution: 30% for sale, 30% for ecosystem incentivization, 20% for the team (2 year vesting), 10% for the company’s future use (2 year lock), 6% for investors, 4% for advisors (2 year vesting).
  • Minimum investment in the presale was $200k, and all presale investors received the same terms: 40% bonus, and 50% of all tokens locked for a 4 month period.
  • The public sale will have an individual max cap on participation, to be set after KYC is completed.
  • Use of funds: 60% for research and development, 25% for marketing, sales, and biz dev, 10% for operations, and 5% for legal, compliance, and governance. The company is being funded solely via the token sale, as well as the 10% reserve for future use.
  • Whitelist: February 8, 2018, Sale: February 21, 2018. KYC Required.

Product

  • Dock.io makes it possible for users to transfer any type of information between apps or platforms and keep their information up to date everywhere. The dock.io app will serve as a connector between apps in the ecosystem, allowing users to manage their information and preferences regarding how information is shared or synced. The app is currently in alpha.
  • The dock.io protocol makes it possible for a third party application to receive push updates from a user about activity on another application, and send back its own updated state. It also makes it possible for third party applications to use business application data (task management, collaboration, file sharing) to assess individual work history and performance, and to create reputation scores, network centrality scores, performance reviews, or even vouch for whether an individual works at a specific company.
  • In dock.io, tokens will be used to incentivize applications to share their data rather than hoard it. Tokens will not be used to incentivize users to share data with applications. When a user sends data from one application to another, the requesting application will pay a fee for access to the data (first to the delivering application, then to be burned). Users will not have any monetary incentive to interact with the product or their data; their benefit will come from having control over their data. The company does currently reward users for inviting friends to the network, to help with early network growth, and plans to continue such efforts until a substantial user base is reached. App fee structures are not discussed. There are no platform fees or rent extraction; the company is funded solely via the token sale.
  • Notable dangers of the model, stated explicitly in the whitepaper, are with regard to applications monopolizing user data or or sharing it without approval, thus effectively undermining the users’ control over their own data, but the model is designed to disincentivize such behavior.

Category Breakdown
Readiness

Is the product ready for use? Is there a working prototype or MVP? How long until it is operational?

3.0
N/A
3 - Prototype / MVP / alpha.
Appeal

How appealing is the product? How good or necessary is it? Does it have a distinct edge?

4.0
N/A
4 - Captivating.
Target User Base

Is it mass market or niche?

3.0
N/A
3 - Has growth potential.
Competition

Are there many other similar solutions or is this one of just a few, or even one of a kind?

4.0
N/A
4 - Few competitors / a leading solution.
Innovation

How innovative or inventive is the product, either conceptually or technologically?

4.0
N/A
4 - Original, specialized.
Product Score:
3.6

Use of Blockchain

  • The dock.io app serves as a connector between apps in the ecosystem. Token costs, as well as any exit fees, will be denominated in Fiat, and a centralized oracle will provide live exchange rates to the dock.io smart contract.
  • Tokens will be used to incentivize applications, not users, to share data. Users will have no monetary incentive, but will benefit from having control over their data.
  • Dock.io utilizes the IPLD2 specification developed for IPFS to perform content addressable data exchange. The unencrypted delta’s of the data format updates are hashed, versioned, and anchored to the Ethereum blockchain using a modified specification of the Chainpoint open standard. This provides data integrity, making it possible for applications to verify the validity of data format updates without exposing the data itself. By encrypting the updates to the different applications’ public keys, the user remains in full control of who receives push updates. (Also, any account can sign the on-chain data format version hashes of any other account, and applications may require the signatures of certain other applications for verification.) Users can also choose to publish unencrypted updates and data to IPFS directly, so as to make them freely accessible. All versioning of the data formats will happen client-side and off-chain. The first implementation will use simple GIT4; the end-goal is a versioned key-value store similar to Noms5.
  • Dock.io data formats are essentially “the equivalent of microformats for Ethereum smart contracts”.

Category Breakdown
Blockchain Development

Is blockchain technology essential? Does it make the solution significantly different and better?

4.0
N/A
4 - Innovative use of blockchain technology.
Disruptive Blockchain Advantage

How disruptive is the introduction of blockchain technology into the product's market space?

4.0
N/A
4 - Generally disruptive.
Need for a Custom Token (vs. BTC or ETH)

Is the token essential or could it be done just as well or better with fiat or Bitcoin?

5.0
N/A
5 - Real, tangible, utility-based value.
System Decentralization (besides token)

How decentralized is the system architecture other than the token (e.g., data collection, storage, access, and use, or decision making processes, etc.)?

4.0
N/A
4 - Mostly decentralized.
Contribution to Blockchain Ecosystem

How compelling is the solution's contribution to the evolution of blockchain infrastructure and economy?

4.0
N/A
4 - Captivating.
Use of Blockchain Score:
4.2

Whitepaper

  • Whitepaper is concise yet detailed, and presents a coherent business model and technical solution overall, but not a concrete development timeline. An unrevealing roadmap is provided elsewhere (on Medium). Whitepaper candidly discloses and explains underlying risks and complexities.
  • Some aspects of the model are still a bit unclear or difficult to understand, and perhaps should be explained better, particularly the token economics, but it appears that quite a bit of thought has gone into creating a token model that supports a truly distributed data economy.

Category Breakdown
Comprehensiveness

Does it cover the full scope of the problem and solution?

4.0
N/A
4 - Satisfactory coverage, well written.
Readability

Is it easy enough to understand?

4.0
N/A
4 - Easy to read and understand.
Transparency

Does it candidly describe and disclose where the project now stands, how much exists and how much still needs to be done, etc.?

4.0
N/A
4 - Informative disclosure.
Business Plan Presentation

Does it contain a viable, comprehensive business plan?

3.0
N/A
3 - More information required.
Technology Presentation

Does it present a well thought out technological architecture? Does it address implementational challenges?

4.0
N/A
4 - Clear, well thought out, realistic.
Whitepaper Score:
3.8

Roadmap

The currently available roadmap lists the following:

  • Jan 2018: Release of the dock.io app (currently in alpha) and Rewards program.
  • Q1 2018: Partnership announcements (currently Remote.com, FundRequest, and SmartRecruiters are mentioned on the website) and Token Sale.
  • Q2 2018: Remote.com Partner Integration followed by additional partner integrations.
  • Q4 2018: Network Data Exchange – applications will be able to exchange data via DOCK tokens with encrypted packages over the IPFS network.

Category Breakdown
Concreteness

Is there a concrete and practical development plan (vs. just a conceptual vision)?

3.0
N/A
3 - An overall plan, major milestones stated.
Feasibility

Is the development plan realistic? Is it based on reasonable goals and timelines?

4.0
N/A
4 - Realistic.
Vision

Is there a larger, long-term vision?

4.0
N/A
4 - Long term.
Dependencies (services or capabilities)

How available, operational, or trusted are the other systems or capabilities on which the project relies?

4.0
N/A
4 - Available and trusted.
Current Position

Where is the project now, relative to its vision and plans?

4.0
N/A
4 - Past a few hurdles.
Roadmap Score:
3.8

Compliance

Generally, the DOCK token provides applications with access to other applications’ user based data. Applications which are also token holders can signal on their contracts which data formats they accept via a simple list with data format names. DOCK token holders also gain voting rights, allowing them to introduce new proposals and vote on the future development roadmap of the protocol, but the mechanism by which this happens (submission and voting process, governance structure, fund allocation, etc.) is yet to be clarified. Token supply is deflationary via burn mechanism.

The company is working with Deloitte, a big four accounting firm, to ensure it is optimally managing funds, as well as with two top US law firms to ensure it is doing everything it can to be compliant. SAFTs are used for presale investors, as well as KYC for every investor, and a few regions are prevented from participating. At the time of token distribution, the network will be live with the full voting utility.

Category Breakdown
Token Utility (value through usage)

How much use is there for the token itself (regardless of its value as an investment vehicle)?

3.0
N/A
3 - Limited or uncertain use cases.
Token as Security (tradable instrument)

How valuable is the token as an investment vehicle or financial instrument?

4.0
N/A
4 - Not as such, or compliance is assured.
Token/Smart-Contract Readiness

Is the blockchain infrastructure of the project ready for use? Is there a working prototype or MVP? How long until it is operational?

3.0
N/A
3 - Prototype / MVP / alpha.
Attention to Compliance Issues

How much attention is given to compliance (via token and ecosystem design, token sale participation, etc.)? Is this issue addressed directly and coherently?

5.0
N/A
5 - Professional, audited.
Legal Review/Risk Assessment

What kind of legal documentation (reviews or agreements) and risk assessment are provided?

4.0
N/A
4 - Professional.
Compliance Score:
3.8

Company and Team

California based Remote.com (the developer and primary integration partner of dock.io) was founded in 2017 and claims over 2 million users.

Cofounder and CEO Nick Macario was previously founder and CEO of branded.me, a professional platform which grew to 3 million+ members and was acquired in Nov 2016 by Outsource.com, a secure marketplace focused on delivering high-quality projects to freelancers. Cofounder and COO Elina Cadouri is also co-founder of Outsource.com. Ten additional team members, mainly developers, are listed, all with active LinkedIn profiles (Remote.com has 35 employees on LinkedIn). Lead Blockchain Engineer Evgeniy Zabolotniy does not list blockchain experience; was Chief Architect at branded.me. Piotr Swies is a Senior Engineer at Remote.com and a Blockchain Engineer at dock.io, “skilled in designing and implementing distributed systems with microservices architecture”.

Category Breakdown
Company Stage and Foundation

Is the company already established? Has it raised funds before? Is it mature?

4.0
N/A
4 - Established with some fundraising history.
Background of Lead Team Members

Do we know who they are? Do they have LinkedIn profiles? Do they have solid, relevant backgrounds?

4.0
N/A
4 - Verifiable relevant experience.
Team Assembly and Commitment

Is a solid, fully committed core team in place? Do they have online (e.g. LinkedIn) profiles showing sufficient relevant experience? Is their participation transparent?

4.0
N/A
4 - Fully assembled and committed.
Team Skill Set Relevance

Does the amount of talent and skill in each area seem to fit the project requirements?

3.0
N/A
3 - Correlated to project requirements.
Team Skill Set Balance

Is the team well-rounded (biz/tech/blockchain)? Is there sufficient talent and skill in all areas of required development?

4.0
N/A
4 - Good, sufficient for each aspect.
Company and Team Score:
3.8

Token Sale

  • Total Supply: 1 Billion tokens
  • Token Price: $0.07
  • Hard Cap: $20M USD (includes both private pre-sale and public sale). The company has already raised $12M through the presale and has a very high likelihood of reaching the $20M target.
  • Token Distribution: 30% for sale, 30% for ecosystem incentivization, 20% for the team (2 year vesting), 10% for the company’s future use (2 year lock), 6% for investors, 4% for advisors (2 year vesting).
  • Minimum investment in the presale was $200k, and all presale investors received the same terms: 40% bonus, and 50% of all tokens locked for a 4 month period.
  • The public sale will have an individual max cap on participation, to be set after KYC is completed.
  • Use of funds: 60% for research and development, 25% for marketing, sales, and biz dev, 10% for operations, and 5% for legal, compliance, and governance. The company is being funded solely via the token sale, as well as the 10% reserve for future use.
  • Whitelist: February 8, 2018, Sale: February 21, 2018. KYC Required.

Category Breakdown
Raise Amount Max

Is there a clear cap? Is the maximum raise amount modestly sufficient (as opposed to either greedy or insufficient)?

4.0
N/A
4 - Well suited to needs and plans.
Raise Amount Min

Is the minimum raise reasonable considering the development plan? Are there raise-amount dependent milestones?

4.0
N/A
4 - Reasonable, sensible.
Fund Allocation

Is fund distribution and allocation reasonable and justified?

4.0
N/A
4 - Well defined and reasonable.
Token Allocation

Is the ratio of tokens sold to those kept reasonable? Does it prevent the company from having too much control?

3.0
N/A
3 - Sufficient company/community interest balance.
Media Presence and Following

Is the sale being talked about in Reddit, Bitcointalk, Social Media, Medium, etc.? Is information available and accessible? Is there interest?

4.0
N/A
4 - Solid exposure and interest, good impression.
Token Sale Score:
3.8
Can you please elaborate on your token model, economics, and governance structure?

Voting:

  • Token holders can introduce new proposals and vote on the future development roadmap of the protocol

Govern data transfer:

  • Tokens are required for applications to pull data from the protocol
  • Tokens are rewarded when applications push data to the protocol, and the data is accepted by other applications in the network
  • Tokens will be burned when multiple platforms request the same data
Are any additional tokens to be issued in the future as more or new applications connect to the platform?

No, 1 billion is the max that will ever be created.

Wouldn't apps be more incentivized to share if all apps accessing their data paid a fee, at least the first time?

Apps are paid each time data is accessed, by the first app who accessed the data/update. If additional apps access the same data/update, those fees are burned. We made this decision to avoid one or two apps in the network controlling large quantities of tokens due to being large data providers (avoids potentially monopolies?).

Will there be any platform fees? What is the company’s own revenue model?

There are no platform fees or rent extraction. The company does not have a revenue model and is funded via the token sale, as well as the 10% reserve for future use. We made this decision to avoid another project forking ours and removing fees to create competition against our project.

Do you have a breakdown of what you can accomplish with different fundraising amounts?

We’ve raised $12 million through our presale and were heavily oversubscribed. Having one of the largest and fastest growing communities in crypto, combined with a moderate max cap target gives us a very high likelihood of reaching our $20 million target.

Do you have a more concrete, detailed development roadmap?

Pleas view our blog about this here.

Do you have concrete plans regarding transitioning to a different or standalone blockchain solution?

We do not. As discussed in our whitepaper, our plan is to use the Ethereum network and if we do run into scaling issues which are not solved by Ethereum roadmap upgrades we will transition to a standalone chain.

Seeing as users already have to have ETH for gas, how is the IPFS system to be maintained and incentivized (e.g. Filecoin)?

Users do not have any interaction with gas fees in regards to data exchange in the dock.io protocol. Applications are responsible for abstracting this from the user experience entirely.

Do you have plans for how to incentivize users to participate on the platform (upload their information, allow sharing between apps)? Or will this be up to the application developers?

We have a program called “Earn” in the App (app.dock.io), which rewards users for contributing to the network. Currently users can earn tokens for inviting friends to the network, which helps with early network growth. We plan to continue and expand these efforts until we reach a substantial user base into the tens of millions.

What kind of regulatory compliance will you be enforcing (KYC, using a SAFT structure, etc.)? Do you have a legal review or agreement? What is the utility value of your token until the platform is fully operational (and when is this expected)?

We work with two of the top law firms in the US, as well as a top four accounting firm in the world to ensure we are doing everything we can to be compliant. We use SAFT’s or presale investors, KYC for every investor, and we are preventing a few regions from participating. We have have a legal memo regarding utility. At the time of token distribution, the network will be live with the full voting utility.

Use this code to share the ratings on your website