bloomtech-labs / anchored.app Goto Github PK

A blockchain enabled verification platform

Anchored utilizes Chainpoint's innovative technology which allows users to securely link a hash of their data, such as important documents, to the Bitcoin blockchain. After logging in, users can connect with third party applications such as DocuSign and get timestamp proofs for any file. By associating data to a tamper-proof, immutable ledger, it can be mathematically proven that the data existed at an exact time and place.

• Jeremy A. Jones
• Zack Hitchcock
• Brandon Aguirre
• Randy Calderon
• Sean Chavez

• Jared Cuffe

• Suniti Thapa

Anchored utilizes Heroku and Netlify for deployment, and is built in full stack JavaScript with a React.js frontend, a Node.js and Express.js backend, a PostgreSQL database in production, and a SQLite3 database in development.

https://anchored.app/

• React

  • Blazing fast rendering with the virtual DOM
  • Robust developer tools for debugging
  • Component based structure maximizes reusablity and makes codebase more maintainable
  • JSX allows for code optimization, type safety and faster creation of templates
  • Unidirectional data flow increases app performance and makes debugging easier
  • API friendly library works seamlessly with and is extendable across numerous frameworks to leverage advanced UI development

• Redux

  • Global app store allows components to listen for change from one source of truth
  • Pure reducer functions make logic easier to test
  • Robust developer tools make it easy to find bugs
  • Strict organization makes code more understandable and easily maintainable

• Styled Components

  • Scopes styles to a component to avoid style leaks
  • Linters will show unused components so they can be removed
  • Source order independence eliminates the need to import files in a certain order
  • Compose new styles from existing components
  • Passing properties to the component allows for more flexibility

https://chainpoint-docusign-server.herokuapp.com/

• Node.js

  • Utilizes Google's V8 JS engine which is lightening fast, highly performant, and more scalable
  • Event loop allows non-blocking I/O operations which enhances speed of code execution
  • Integrates seamlessly with microservices architecture
  • Fullstack JS allows JS developers to work on both client and server sides potentially increasing productivity and saving money for startups

• Express

  • Includes numerous routing features and separate handlers for HTTP methods
  • Serves static files such as images and CSS / JS files
  • Integrates seamlessly with many popular template engine and NPM module plugins

• PostgreSQL

  • Supports many data types
  • Strongly typed schemas leaves little room for errors
  • Superior query optimizer for more complex data models

• DocuSign

  • We pull in user documents via DocuSign's API to our database, flag them, and then filter them on the client-side based on five categories:
    • All Documents
    • Anchored Documents
    • Documents Pending Anchor
    • Signed Documents Awaiting Anchor
    • Unsigned Documents Awaiting Signatures

• Chainpoint

  • When a user verifies they would like to anchor their document, we send a hash of that data to Chainpoint, which is aggregrated with other hashes using a Merkle tree. The root of the tree is published in a Bitcoin transaction, which cryptographically links the given data to a block on the Bitcoin blockchain.

• Stripe

  • Users can purchase the number of credits they want with a valid credit card, which is verified and charged via Stripe.

• Auth0

  • Users can sign up / log in using a social media or enterprise account or their own email address. Auth0 handles authentication and authorization for more secure sign ups and log ins.

* denotes required field.

We chose Auth0 to handle authentication, which allows users to sign up or log in with Google or Twitter, or with their own email and password. When a user initially signs up, their data is stored on our database and saved as a session. If a user is already signed up, when they log in, the session will pull the user's data from the database and serve it to the client.

We used middleware in our routes to ensure that when a user hits a protected endpoint, they must be authenticated. Inside of the app, when a user first logs in to their DocuSign account, their DocuSign data is stored to the database and appended to the current session. After this authentication process, we pull the user's documents via the DocuSign API, store them on our database, and serve them to the client.

We used Stripe to securely verify user credit cards and payments. After a user submits a payment, if it is successful, Stripe will send back a response that lets us know that their payment was valid as well as an invoice that we save to our database. Once this is complete, a user's credits will be dynamically updated. With the help of Stripe, this ensures that a user cannot hack us and manually update their credits without paying first.

DocuSign logo - https://www.docusign.com/company/terms-and-conditions/developers