For backend, it will take 10 ~ 20 days to complete all tasks, and it may take some days for the penetration test. 2-3 days for the frontend part implementation, once the Credential manager and oAuth support is ready on the backend. A week with testing and some padding.With some padding we can target Oct 3 for the launch.

Question: When will we have what Nexus features to launch?


Currently we leak many secrets to the client-side which is only tolerable in testing and must be fixed before launching. Estimated 2 ~ 5h on backend side, then 


Update OAuth authorization and API call URL 


@Egor Milyukov  and  @Jin  will need to update OAuth authorization and API call URL to route calls through credential manager and avoid touching any credentials. Implement a more secure sign in process. Currently the Metamask sign in process is not very secure (anyone who knows public key of the user can sign in). We need to improve it to at least verify that user owns the private key in Metamask. Estimated 1 ~ 2h on server-side. Estimated 4-8hrs on frontend side.


We also will need to implement oAuth flow for Nexus users, so our app/api can be properly integrated with Zapier, see my conversation with Zapier app developer: 

https://inboundlabs.slack.com/archives/C03QY6D2YDT/p1660682917596499

. Estimated 1 ~ 3h on server-side. Estimated 1-3h for frontend.

@Egor Milyukov will need to implement message signing on the front-end. Estimation included above in the “update oAuth” section.


Implement calling smart contract from unique proxy address for each user. Currently the web3 connector calls smart contract function from a fixed address owned by us, which is obviously not really useful. We will need to implement logic to route the call via a proxy address, which is dynamically generated for each user. This involves some smart contract programming (for routing calls) and I will need to research it, estimated 5 ~ 10h for EVM chains, 4 ~ 8h for Near and 4 ~ 8h for Flow.


Perform general security review on all components and fix any security issues. Estimated 3 ~ 6h. We may also get a security firm to run a penetration test on our infrastructure.


Question: When will we have the simplest for of Gas Payments to have a bi-directional system?


The simplest form will be user manually transferring some gas token to the proxy address for use by Nexus. This is of course not user-friendly, but requires little to no additional work on our end.


What is missing for the different types of developments (web3 CDS, Blockchain Driver, Web2 Driver, App) to be complete? (we also need this to deliver grants commitments). Starting here.


Product OKR Planning 16-8-22

grindery

Business

Welcome

Courses

Miscellaneous

Funding and Grants

Grindery Planning Sessions: August 2022

Onboarding

gWork

Developers

Review

Partners

Active Topics

Grindery Nexus Feedback 2.0

Grindery Nexus Feedback

Demo Day Priority

Nexus Review 3

Grindery: A Simple Plan

Team

External Document List

Snapshot App development

Grindery Sanity Check

Developing Web3 Connectors

Grindery Payment Rails

Grindery Payment Rails - Celer

Demo Day Connectors

Roadmap

Grindery Grant Program (WEB)

Grindery Infinite Fundrising (9-6-2022) - current

Grindery Infinite Fundraising

Harmony DAO

The Graph

Storage

Snapshot-XMTP-Grindery

ANKR x Grindery.io

ANKR

Chain Partnerships

XMTP

Ceramic

Celer

(d)Apps 

DAOs/Multisgs

Cosmos/Ignite 

Binance BSA

Polkadot 

Orientation for New Hires

Understand Grindery & its projects

Orientation

Grindery 101

Co-creation Slide

Co-creation

Marketing

Funding/Investing - Inbound/Outbound

Funding/Investing

Knowledge Management_Operations

Grindery DAO Sales Process

Grindery Unified Marketing

Grindery Marketing

Grindery OKRs

On Token Allocation

On Connectors

On Community 

On Organization

On Tokenomics

On Brand

On Roadmap 

On Validation

Grindery Culture Slide

Grindery Culture: Habits and Practices

How to get paid at Grindery

Grindery Payment Policy

Getting started at Grindery

Grindery OAuth 2.0

Grindery Zapier (Dimitri)

Grindery Zapier (James)

Grindery Zapier (Mohammed)

Grindery Zapier (Richard)

Grindery Zapier (Alek)

Grindery Zapier App Test Task

Grindery DePay

Grindery Nexus Authentication Process

Get started: Grindery Progressive Scope

Grindery Integration Options

CDS Editor

Creating Blockchain Connectors

Grindery - Cross chain technologies (copy)

Grindery DePay Router Protocol

A guide to FLOW CDS

Conector Analysis

Grindery Ping Feature RoadMap

Gnosis Safe App Dev

Grindery Connector Roadmap

SDK Documentation

Module 4: How to get paid at Grindery

Module 3: Grindery Payment Policy

Module 2: Grindery Culture, Habits and Practices

Module 1: A brief history of Grindery

Exercise: Detect a transfer on any EVM chain

Grindery