Kendall Cole
Kendall Cole
***Problem*** Currently, apps must always have their users "login" via the NEAR Wallet by adding an access key, before they can sign any transaction that includes a NEAR deposit. This...
1. 1. Story As an app developer, I want to fund the creation of my users` accounts, so they can login and use my app. 1. 1. Flow 1\. Generate...
### Overview Critical user journeys should be covered by end-to-end tests using a testing framework like [Cypress](https://cypress.io). ### User Journeys - [ ] Create new account - [ ] Setup...
### Overview We currently use Mixpanel and Sentry for analytics and bug tracking. We've implemented data scrubbing of sensitive data, but should consider a more complete and future proof solution....
See https://app.zenhub.com/workspaces/chainmiddleware-5cea2bcf78297c385cf0ec81/issues/nearprotocol/nearcore/2167 ## Story As a user, I want to view the arguments of a contract call in a readable format whether they are in JSON or Borsh. ## Acceptance...
## Story As a user of the Explorer looking into an Account's page, I want to filter transactions by different actions (functionCall, etc), so I can determine whether an account...
## Story As a user, I want to see a list of contracts on NEAR, so I can determine the most used contracts and better understand what NEAR is used...
### Overview Contract interactions are likely to make up a major portion (if not the majority) of the activity on NEAR. Users, both developers and end users, will want to...
### Overview The current Ledger login implementation requires users to add all accounts associated with their Ledger at once. If they reject an account (confirming the "add key" TX), the...
### Overview We're experiencing issues with users "mining" the faucet to accumulate large amounts of NEAR. To prevent this, we should implement rate limiting by IP address. Relevant route: https://github.com/near/near-contract-helper/blob/master/app.js#L83...