# NEAR Lake Support by FASTNEAR\\n\\n## Organization\\n\\nFASTNEAR\\n\\n### Primary person\\\'s contact information\\nEvgeny Kuzyakov (ek@fastnear.com)\\n\\n### About\\n\\n[FASTNEAR](https://fastnear.com) is NEAR Protocol Infrastructure Provider.\\n\\n#### [Services](https://fastnear.com/services)\\n- RPC endpoints\\n- API for wallets\\n- Snapshot data\\n- Indexing and Lake solutions (see https://neardata.xyz)\\n- Validator services\\n\\n#### Key Features\\n1. **Dedicated to NEAR Protocol:** We exclusively serve the NEAR ecosystem.\\n2. **High-Performance Infrastructure:** \\n   - The majority of nodes and servers hosted on bare-metal.\\n   - Currently handling ~4,000 RPC requests per second. Resulting in 320M calls per day.\\n\\n#### Reliability and Security\\n- Experienced in handling:\\n  - Traffic surges of 30,000 RPS\\n  - DDoS attacks (recently)\\n  - Provider outages\\n  - Testnet/mainnet issues\\n- Free NEAR Lake alternative at https://neardata.xyz\\n\\n#### Monitoring and Performance\\n- Internal monitoring and alert systems\\n- External status page https://status.fastnear.com\\n\\n## Body\\n\\n### (Background) NEARDATA by FASTNEAR\\n\\nFASTNEAR provides a simple and free alternative to the publicly available S3-based service NEAR Lake Framework called NEARDATA (https://neardata.xyz).\\n\\nFeatures:\\n- Data is grouped by blocks.\\n- Data is accessible through HTTPS for free.\\n- Each `ExecutionOutcome` for every Action Receipt contains originating transaction hash.\\n- Data is cached locally and by Cloudflare.\\n- Ability to read blocks from the browser.\\n- Ability to get recent optimistic blocks.\\n- Ability to download raw archived data. Useful for backfills.\\n\\nExample of the blocks timestamp to the wall time latency from NEARDATA:\\n![NEARDATA Latency](https://gist.github.com/user-attachments/assets/f0033340-0d66-4c92-be45-14e632bb9df8)\\n\\nFASTNEAR is already indexing and serving the following:\\n- NEAR Mainnet Final blocks\\n- NEAR Mainnet Optimistic blocks (with an average of 1- second wall to block-timestamp latency)\\n- NEAR Testnet Final blocks https://testnet.neardata.xyz\\n- NEAR Testnet Optimistic blocks\\n\\nWe provide data in the following formats:\\n- Full indexed blocks (including all data for all shards) in JSON file accessible throught HTTPS. Examples:\\n    - Latest finalized mainnet block: https://mainnet.neardata.xyz/v0/last_block/final\\n    - Latest optimistic mainnet block: https://mainnet.neardata.xyz/v0/last_block/optimistic\\n    - Latest finalized testnet block: https://testnet.neardata.xyz/v0/last_block/final\\n    - Block `123456789` on mainnet: https://mainnet.neardata.xyz/v0/block/123456789\\n    - Block `123456789` on testnet: https://testnet.neardata.xyz/v0/block/123456789\\n- Pending finalized blocks. When you request a block by height that is close to the head, but is not produced yet, the server will hold the connection until the block becomes available. Making it easy to implement indexers.\\n- Archival data by 10 block archives, allows to quickly backfill data. Available for mainnet and testnet:\\n    - Older mainnet data: https://a0.mainnet.neardata.xyz/raw/\\n    - Recent mainnet data: https://mainnet.neardata.xyz/raw/\\n    - Testnet data: https://mainnet.neardata.xyz/raw/\\n\\nThe whole indexing and servers are open-sourced with README: https://github.com/fastnear/neardata-server\\n \\n### Proposal\\n\\nFASTNEAR offers support for the existing S3-based NEAR Lake solution.\\n\\nWe\\\'ll utilize existing indexing NEARDATA nodes to also write data to the S3-based NEAR Lake.\\n\\n### Cost estimates\\n\\n#### Nodes\\n\\nWe don\\\'t include the cost of the hardware nodes into this proposal, because we are already covering it as part of NEARDATA. Consider the nodes cost included into the monthly maintenance fee.\\n\\nNote, that in the future a single node for all shards might not be sufficient, so indexing nodes will need to produce shards independently. That\\\'s where our expertise of the customized setups will be helpful.\\n\\n#### S3\\n\\nThere is very good S3 cost estimate provided in the following proposal by Aurora Labs: https://near.social/infrastructure-committee.near/widget/app?page=proposal&id=28\\n\\nWe recommend a few adjustments to the estimate:\\n- The storage might grow due to the increase in the number of shards. Rumors are there will be 10 shards by the EOY, which might increase throughput of the network and the amount of data.\\n- Target blocks per second should be `1`.\\n- The current storage is around 40Tb for the mainnet and 8Tb for the testnet.\\n\\nBreakdown:\\n- S3 storage per month (at 84Tb avg): $2107.39\\n- Estimated objects per network per month: 28,908,000\\n- Writes per month: $936.6\\n- Reads per month: $63\\n- Safety margin: 20%\\n- Total: **$3804 per month**\\n\\n#### Maintenance\\n\\nWe ask for **$8,000** a month for maintenance and support.\\n\\n## Goals / Milestones\\n\\n- Knowledge transfer (1 week)\\n- Setup nodes once the write access is received (1 week)\\n- Transfer of S3 bucket ownership\\n- Dedicated status page entry (2 weeks)\\n- Public latency monitoring dashboard (2 weeks)\\n- Documentation updates if necessary (4 weeks)\\n\\n## Metrics\\n\\n- Block timestamp to wall latency (expected most blocks to be available under 5 seconds). Similar to a live latency test from NEARDATA https://neardata.xyz/\\n- Uptime (expected 99.9%)\\n- Consistency: no-skipped data\\n\\n### Compensation\\n\\nFor maintenance and development we ask for $12,000 a month.\\n\\n## Budget\\n\\n$11,800 per month (paid monthly) for the duration of 12 months.\\n- $3,800 AWS S3\\n- $8,000 maintenance \\n

NEAR Lake Support by FASTNEAR

Support NEAR Lake by FASTNEAR by utilizing existing nodes from NEARDATA

	Receipt	Action	Method	From		To	Value	Gas Limit

Detalye ng Transaksyon

Overview

Execution Plan

Enhanced Plan

Tree Plan

Receipt Summary

Comments