## Overview\\n\\nKit Wallet Indexer API is an undocumented but widely used lightweight indexer that helps to find user\\u{2019}s FTs, NFTs, and accounts by public key, that builds off of [NEAR Lake Framework](https://docs.near.org/concepts/advanced/near-lake-framework) (which also has an RFP). As [Pagoda winds down its services](https://docs.near.org/blog/2024-08-13-pagoda-services), there is a need to transition the management and development of the Kit Wallet Indexer to a capable service provider. The transition aims to ensure uninterrupted service of this vital data infrastructure, which is essential for various stakeholders in the NEAR ecosystem.\\n\\n* Indexer Endpoints API: [https://github.com/near/near-contract-helper/blob/master/indexer.js](https://github.com/near/near-contract-helper/blob/master/indexer.js)\\n* Indexer Endpoints Code: [https://github.com/near/near-contract-helper/blob/master/src/middleware/indexer.js](https://github.com/near/near-contract-helper/blob/master/src/middleware/indexer.js)\\n\\n**Current live endpoints**\\n\\n* Mainnet [https://api.kitwallet.app/](https://api.kitwallet.app/) (currently hosted on AWS)\\n* Testnet [https://testnet-api.kitwallet.app/](https://testnet-api.kitwallet.app/)\\n\\n## Requirements\\n\\n**Include the following endpoints on mainnet and testnet:**\\n\\n* router.get(\\\'/publicKey/:publicKey/accounts\\\', findAccountsByPublicKey);\\n* router.get(\\\'/staking-deposits/:accountId\\\', findStakingDeposits);\\n* router.get(\\\'/account/:accountId/activity\\\', findAccountActivity);\\n* router.get(\\\'/account/:accountId/callReceivers\\\', findReceivers);\\n* router.get(\\\'/account/:accountId/likelyTokens\\\', findLikelyTokens);\\n* router.get(\\\'/account/:accountId/likelyNFTs\\\', findLikelyNFTs);\\n* router.get(\\\'/account/:accountId/likelyTokensFromBlock\\\', findLikelyTokensFromBlock);\\n* router.get(\\\'/account/:accountId/likelyNFTsFromBlock\\\', findLikelyNFTsFromBlock);\\n* router.get(\\\'/stakingPools\\\', findStakingPools);\\n\\n**An instance of PostgresSQL, copy of databases, and implemented as follows:**\\nhttps://github.com/near/near-contract-helper/blob/master/src/middleware/indexer.js#L11\\n\\n## Usage \\n\\nThe graph below indicates the most recent usage for the past months KitWallet LB requests: ~350K per day (average response time is less than 0.14 seconds, but there are spikes of 50 seconds or more currently)\\n\\n![alt_text](https://github.com/user-attachments/assets/a5b10c0a-7aba-4d44-bd33-7a5ae05e42e1 \\\"image_tooltip\\\")\\n\\n![alt_text](https://github.com/user-attachments/assets/7c4fc10a-8b12-48be-be65-c1b01336b7d5 \\\"image_tooltip\\\")\\n\\n_Note: the majority of endpoint usage, [FastNear](https://github.com/fastnear/fastnear-api-server-rs) already supports_\\n\\nThis Kit Wallet Indexer API is undocumented and not officially supported.  Because of this, many wallets that are more NEAR \\u{201c}native\\u{201d} have already switched to other solutions like [FastNEAR](https://github.com/fastnear/fastnear-api-server-rs).  But there are still many [non-custodial](https://github.com/near/wallet-selector) and exchange wallets that depend on the Kit Wallet Indexer service or that we are still confirming their usage. \\n\\nWe do not have data available which NEAR ecosystem projects are currently using Kit Wallet Indexer but these should include wallets and exchanges and any projects that need to quickly query different token balances.\\n\\nEcosystem projects that have already  transitioned off of Kit Wallet to better-maintained services include [Nightly](https://nightly.app/), [Meteor Wallet](https://wallet.meteorwallet.app/), MyNEARWallet, NEAR Mobile Wallet, and [Bitte/Mintbase Wallet](wallet.bitte.ai).\\n\\n#### Monitoring, Alerting, Reporting\\n\\n* \\u{200b}\\u{200b}Real-time monitoring of system health and performance with public forward facing status page\\n* Alerts for data inconsistencies or indexing delays and public channel & direct communication with major stakeholders using service\\n* Internal Dashboard for visualizing system metrics\\n* Weekly progress reports during the transition phase to Infrastructure committee asynchronous \\n* Quarterly performance and usage reports\\n\\n#### Documentation\\n\\n**As part of this transition, maintenance, and proposals, please include;**\\n\\n* Comprehensive system architecture documentation\\n* API documentation including usage examples (mentioning the service will be deprecated and linked to alternative solutions like _[FastNear](https://github.com/fastnear/fastnear-api-server-rs) _) \\n* User guide for common queries and use cases.\\n\\n### Transition Steps for selected vendor\\n\\n1. Review and understand the current Kit Wallet Indexer API infrastructure (including accompanying infra like NEAR Lake) and processes.\\n2. Include detailed transition plan,in your milestones\\n3. Set up necessary access and permissions for the new team.\\n4. Conduct knowledge transfer sessions with the current Pagoda team.\\n5. Implement and test any necessary changes or improvements to the infrastructure.\\n6. Perform thorough testing to ensure data integrity and system performance.\\n7. Update all relevant documentation.\\n8. Gradually transition operational responsibilities.\\n9. Establish new support channels and processes.\\n10. Conduct a final review and handover with the Infrastructure Committee.\\n11. Conduct official communications on your channels and with the NEAR Developer ecosystems and relevant stakeholders\\n12. As part of this RFP and based on current usage, the goal is to provide this as a public good. Part of this transition strategy may include pushing users to alternatives like FastNEAR API. \\n13. Estimated transition time, not taking into account any KYC or KYB blockers, is 1 week.  \\n\\n### Service Level Agreements\\n\\n1. **Availability**\\n    * **Uptime Guarantee**: 99.0% monthly uptime\\n    * **Downtime Allowance**: Up to 0.1% of downtime per month\\n2. **Performance**:\\n    * *This should be tracked internally and shared with Infrastructure Committee (IC)*\\n    * **Response Time**:\\n        * Better or in line with existing response time.\\n    * **Rate Limiting**:\\n        * Please outline your rate limiting plan to continue to support Kit Wallet as a public good, if applicable. \\n3. **Support**\\n* **Support Availability**: Community-based support only (e.g., through forums, GitHub issues, or a developer community Slack/Telegram/Discord channel)\\n* **Response Time**: No guaranteed response time, but best-effort responses within 24-48 hours. A single point of contact for urgent issues.\\n4. **Data Integrity**\\n* **Data Consistency**: \\n    * Ensure that there is data validation in place (to show proper information). \\n    * Proper backup of data is maintained and the data is up to date. \\n5. **Updates and Changes**\\n* **Notice for Breaking Changes**: At least 7 days\\\' notice for any breaking changes in the API or infrastructure\\n* **Versioning**: Ensure that the new API versions will be backward-compatible wherever possible.\\n* Maintenance - Proper updates to the community and stakeholders about any major maintenance which could impact the service, experience and uptime of the API adversely. \\n6. **Limitations**\\n    * **No SLA Credits**: No financial credits or compensation for outages or performance issues for free public good services. \\n    * **Fair Use Policy**: Provide Explicit statements about the intended use for development and the prohibition of production workloads\\n7. **Termination Rights**: The right to suspend or terminate the service for users who exceed fair use or misuse the service. IC must be informed about these.\\n8. **Failure to Perform:** If Kit Wallet maintenance falls below the performance aforementioned benchmarks, the Infrastructure Committee has the right to transition this public good to another vendor. The current maintainer will be required to facilitate the transition. \\n\\n### Budget Guidelines\\n\\n* **Budget**: Proposals should outline a **detailed budget**. A clear breakdown of costs, including development, testing, documentation, maintenance & support, infrastructure, 3rd party services and external API costs. Maintenance cost should be calculated accurately based on provided usage information and existing software costs. Being able to properly assess a budget based on usage is a major factor for qualifying legitimate vendors.\\n* **Milestones**: Please highlight the details of the various milestones that are included in your development plan and relevant budgets attached to each milestone. Any metrics around success of the milestone (acceptance criterion) should also be included. Milestone examples include upon signing of agreement, upon official transition, 6 month billing period, 12 month billing period, \\u{2026} and so forth. \\n* **Contingency**: Include a contingency plan for potential overruns or unexpected expenses. In the event that expense for providing free or a public good to the NEAR ecosystem, there should be a clear policy to report expenses incurred by NEAR usage to cover additional costs and prove that costs exceeded previous budgets. \\n\\n### Required Experience\\n\\n* **Experience:** Proven experience in big data processing, cloud infrastructure management, and blockchain data indexing, preferably within the blockchain or fintech sectors. Experience working with NEAR Protocol is a plus.\\n* **Portfolio:** Examples of previous work and case studies demonstrating success in similar projects.\\n* **Team:** A skilled team comprising developers, data engineers, and support staff with relevant experience.\\n* **Relevant Business:** Demonstrate that your team has an existing business that would motivate you to continue building and maintaining this infrastructure\\n\\n## Resources\\n\\n**Alternatives to Kit Wallet;**\\n\\n* Fast NEAR API Server: [https://github.com/fastnear/fastnear-api-server-rs](https://github.com/fastnear/fastnear-api-server-rs) (hosted free alternative)\\n* Pagoda enhanced api: [https://console.pagoda.co/apis?tab=enhancedApi#/](https://console.pagoda.co/apis?tab=enhancedApi#/) \\n* NEARBlocks api: [https://api.nearblocks.io/v1/account/rektdegen.near/inventory](https://api.nearblocks.io/v1/account/rektdegen.near/inventory) \\n* HERE Wallet ZMQ Indexer [https://github.com/here-wallet/near-zmq-indexer](https://github.com/here-wallet/near-zmq-indexer)  \\n* [Mintbase Indexer](https://docs.mintbase.xyz/dev/mintbase-graph) [https://github.com/here-wallet/near-zmq-indexer](https://github.com/here-wallet/near-zmq-indexer) \\n\\n**Support;** \\n\\n* NEAR Indexer Working Group [https://nearbuilders.com/tg-data](https://nearbuilders.com/tg-data) \\n\\n**Kit Wallet Resources;**\\n\\n* [https://github.com/near/near-contract-helper](https://github.com/near/near-contract-helper)\\n* Indexer Endpoints API: [https://github.com/near/near-contract-helper/blob/master/indexer.js](https://github.com/near/near-contract-helper/blob/master/indexer.js)\\n* Indexer Endpoints Code: [https://github.com/near/near-contract-helper/blob/master/src/middleware/indexer.js](https://github.com/near/near-contract-helper/blob/master/src/middleware/indexer.js)\\n\\n**Past Proposals;**\\n\\n* HERE Wallet [https://gov.near.org/t/proposal-develop-public-near-indexer-from-here-wallet-team-compatible-with-kitwallet-api/37307](https://gov.near.org/t/proposal-develop-public-near-indexer-from-here-wallet-team-compatible-with-kitwallet-api/37307)\\n\\n## Process\\n\\n**[Proposal Process](https://docs.google.com/document/d/1F7iAT9tWngik9JPS_GadCCEB5nZtA2AiL2yWZoBGMFM/pub)**\\n\\nYou should submit a proposal in response to this RFP on the Infrastructure Committee Portal. [Here](https://docs.google.com/document/d/1TVvPXPJhZfaFwfA2UMW6c3pO2kis45SJ1Np1XOkkhnA/edit?usp=sharing) is a standard (+ [markup](https://docs.google.com/document/d/1UZRfOE1JAOhsnSmp-RmL2hY7KPJbpBImKZVvPV4YJmA/edit?usp=sharing)) template you can use as a starting point. \\n\\nMarketing materials, presentations, and images can be attached as needed as external links. An easy way to do this is to start a discussion under the Proposals category on the Infrastructure Working Group GitHub repository [here](https://github.com/near/Infrastructure-Working-Group/discussions/categories/proposals), publish, then edit and copy the links generated to the files you uploaded.\\n\\n#### Proposal Submission Dates\\n\\nThe deadline for proposal submission is **Tuesday, October 15th** (giving applicants approximately three weeks), with a Q&A period on the proposal itself. We will accept submissions after this date, however, on-time proposals will take priority.\\n\\n### Selection Process\\n\\nAfter reviewing the proposals, the committee will vote on the best one. Generally, this process takes two working weeks to complete and will be discussed and voted on at the regular bi-weekly meeting.\\n\\n#### Voting Dates\\n\\nThe estimate for voting completion is **two weeks** after the proposal submission date.\\n\\n### Transition Process\\n\\nThe estimated transition time is one week, not considering any KYC or KYB blockers.  \\n\\n### Funding Process\\n\\nThe Infrastructure Committee governs funding with assistance from the NEAR Foundation. If selected, your proposal enters the funding pipeline. You are required to:\\n\\n* Complete the KYC/B process conducted by the NEAR Foundation, including verification by IDVerify.\\n* Sign a legal agreement regarding the work as outlined in the proposal conducted by the NEAR Foundation.\\n* Submit an invoice to NEAR Foundation Finance outlining how you want funds disbursed, to what wallets or banks, and in the agreed-upon amounts.\\n* Complete a test transaction to verify target wallets (when requesting funds in cryptocurrency).\\n\\n#### Funding Dates\\n\\nThe funding process is generally completed in one working week if the proposal does not require clarifications in the budget, work approach, legal agreement, or invoicing terms.\\n\\n## Communication\\n\\nPlease direct all communications to the thread where the RFP started beneath the submitted proposal. Please direct confidential or sensitive communications to the Telegram group set up between the committee and the organization/entity/team. If you don\\\'t have a private Telegram group between your team and the Infrastructure Committee, please request one in this thread.\\n\\n

Kit Wallet Indexer API

Kit Wallet Indexer API is an undocumented but widely used lightweight indexer that helps to find user\\u{2019}s FTs, NFTs, and accounts by public key, that builds off of [NEAR Lake Framework](https://docs.near.org/concepts/advanced/near-lake-framework) (which also has an RFP). As [Pagoda winds down its services](https://docs.near.org/blog/2024-08-13-pagoda-services), there is a need to transition the management and development of the Kit Wallet Indexer to a capable service provider.

	Receipt	Action	Method	发送方		接收方	Value	Gas Limit

交易详情

Overview

Execution Plan

Enhanced Plan

Tree Plan

Receipt Summary

Comments