Transaction: Fc7DWdW...4LF1

{ "data": { "neardevnews.community.devhub.near": { "blog": { "near-dev-news-10-3232": { "": "Welcome to the milestone **10th edition of NEAR Dev NEWS!** 🎉 To celebrate this , we've got something special in store for motivated web2 and web3 developers. Introducing our **Bounty Boost Program,** designed to reward the developers who win hackathons using NEAR tools. Keep reading for all the details.\n\nIn this edition, we'll explore the latest updates, highlight weekly activities, and developer opportunities with NEAR.\n\n  \n### FEATURED RELEASES & PR's 🤩\n- 🚀 [**`near.cli.rs`**](https://near.cli.rs/) has new releases [0.9.0](https://github.com/near/near-cli-rs/releases/tag/v0.9.0) and [0.9.1](https://github.com/near/near-cli-rs/releases/tag/v0.9.1)\nEnjoy even more help from CLI selecting the functions to interact if the contract supports NEAR ABI!\n\n- **`near-jsonrpc-client-rs` Version 0.9.0 has been released:**\n - A new release of `near-jsonrpc-client-rs` version 0.9.0 was announced. This release includes improvements to the RPC server in nearcore. The update was credited to a specific contributor and was accompanied by gratitude for testing and final tweaks before release.\n - Check it out on 👉 [GitHub](https://github.com/near/near-jsonrpc-client-rs/releases/tag/0.9.0)\n\n- **`near-api-js` Version 4.0.1 has been released:**\n - This includes support for the new `send_tx` function. The update allows all transaction sending functions to utilize the new function, providing improved functionality for developers!\n\n- `near-rust-sdk` **version 5.1.0 has been released**. The highlights of the release can be found 👉 [here](https://github.com/near/near-sdk-rs/releases/tag/near-sdk-v5.1.0).\n\n- `Wallet Selector` **Version 8.9.6 has been released**:\n\n👉 Github --> https://github.com/near/wallet-selector/tree/v8.9.6\n👉 NPM --> https://www.npmjs.com/package/@near-wallet-selector/core\n\n- Discover more in releases and merged pull requests in our changelog 👉 [here](https://docs.near.org/changelog/2024/02/29/#-documentation).\n\n  \n### DEVELOPER UPDATES 🛠\n\n\n1. **SDK 5.1 Migration Issues**: \n\nDevelopers encountered challenges migrating from `#[near_bindgen]` to the `#[near]` macro in SDK 5.1. An error occurred during ABI extraction, citing a lack of NEAR ABI symbols in the dylib. The issue was reported along with the relevant console command for reproduction. A GitHub branch was created for further investigation. 👉 [GitHub Issue](https://github.com/near/near-sdk-rs/issues)\n\n2. **Serialization of u64/u128 in SDK 5.1**: \n\nQuestions arose regarding the automatic serialization of `u64` and `u128` as strings for input/output in SDK 5.1. Developers observed discrepancies in return values between using primitive types and their corresponding `U64` and `U128` wrapper types. Community members discussed implications for contract interoperability with near-api-js and potential solutions to maintain consistent data representation. \n\n3. **Proposal for Privacy and Encryption SDK**: \n\nA proposal was submitted to DevHub for the development of a privacy and encryption SDK for NEAR. The proposal aims to enhance privacy features and data security on the NEAR platform. Community members were invited to review the proposal and provide feedback. The proposal includes details on the team involved and the objectives of the SDK. \n\n4. `near-cli-rs` **Enhancement** : \n\nWe're improving near-cli-rs to display transaction fees in NEAR tokens and USD after each transaction. This enhancement offers users greater transparency and clarity regarding transaction costs. The proposed changes will involve modifying the `print_transaction_status` function in the `common.rs` file. This function will now include information about transaction fees, specifically the gas amount in the `ExecutionOutcomeView::gas_burnt` field.\n\n Follow the progress on [Issue #320](https://github.com/near/near-cli-rs/issues/320).\n\n5. **Ui is NEAR Project Updates**: \n\nProgress updates were provided for the Ui is NEAR project, highlighting the completion of 15 components along with their respective functionality tests. The project aims to enhance the user interface experience for NEAR-based applications. The proposal link was shared for further information on the project's scope and objectives. 👉 [DevHub Proposal](https://near.social/devhub.near/widget/app?page=proposal&id=62)\n\n6. **Integration of NEAR Data on LangChainAI via Mintbase API**: \n\nNEAR Protocol data is now accessible on LangChainAI through the Mintbase API. Community members were encouraged to explore the integration, which provides access to on-chain data for analysis and development purposes. A link to the documentation detailing the integration process was shared for reference. 👉[Documentation](https://github.com/langchain-ai/langchain/blob/master/docs/docs/integrations/document_loaders/mintbase.ipynb)\n\n7. **NEP-536 and NEP-540 Approval Voting in Protocol Work Group Call #9:**\n\n In the recent Protocol Work Group call #9, NEP-536, which suggests adjustments to gas refunds, received positive feedback from all four working group members, leaning towards approval. However, NEP-540, focusing on storage staking adjustments, was unanimously rejected due to concerns regarding potential risks and limitations. 👉 [Recording](https://www.youtube.com/watch?v=FPGNFDQ6rRA&t=429s&pp=ygULbmVhciBkZXZodWI%3D)\n\n8. **API Updates for NEAR Transactions and Account Information:**\n\n Developers can now access transaction counts and account information via NEAR's API services. API3.NearBlocks.io provides endpoints for fetching transaction counts for specific accounts, while PikesPeak.ai offers similar functionality with authorization requirements. 👉 [API3 NearBlocks](https://api3.nearblocks.io/v1/account/slimedragon.near/txns/count) | [PikesPeak.ai](https://api.pikespeak.ai/account/tx-count/slimedragon.near)\n\n9. **Protocol Update for Implicit Account Functionality:**\n\n The NEAR protocol update addresses issues with hex names and implicit accounts, ensuring compatibility and security by requiring non-0-9-a-f characters as the last character in account names. This prevents potential vulnerabilities related to implicit wallet transactions. \n\n10. **Intermediate Level Course Proposal on Promises and Asynchronous Smart Contracts**:\n\n - Community members proposed a new course idea focusing on Promises and their runtime interaction, tailored for an intermediate level audience. The course aims to delve into topics such as atomicity and designing asynchronous smart contracts effectively. Roman discussed the challenges of implementing a token swap scenario involving two fungible token contracts on NEAR's asynchronous platform.\n - Source: 👉 [NEAR Protocol Forum](https://gov.near.org/t/intermediate-level-course-proposal-on-promises-and-asynchronous-smart-contracts/5071)\n\n11. **DEX Intermediaries for Token Swapping**:\n\n - Doc contributors suggested the use of intermediaries in decentralized exchanges (DEX) to facilitate token swapping, mitigating the risk of state changes in case of transaction failure. This approach involves a DEX acting as an intermediary to handle token swaps and ensure transaction atomicity.\n\n12. **Testing Best Practices and Documentation Improvement**:\n\n - The documentation maintainer highlighted the importance of testing smart contracts thoroughly before deployment and suggested updating documentation to emphasize testing using workspaces over direct deployment to the network. He proposed a shift towards encouraging users to write tests that verify the expected behavior of functions.\n - Source: 👉 [NEAR Protocol Forum Issue](https://github.com/near/docs/issues/1930)\n\n13. **Enhancement Proposal for Account Creation Documentation**:\n\n - Documentation contributors raised a proposal to improve documentation regarding account creation, suggesting the inclusion of instructions for creating accounts through plain contract calls in addition to CLI and sub-accounts. The aim is to provide comprehensive guidance on account creation methods.\n\n14. **Cypherock Cover Announcement**:\n\n Cypherock Cover has been introduced as the industry's first multi-chain, non-custodial, and non-KYC inheritance-style recovery service for cryptocurrencies. The service offers early access to users and an additional year of service for early adopters. 👉[Twitter Announcement](https://twitter.com/rohanagarwal94/status/1782504675620655176?t=IbnJY4UuHD_nzrl90N08LQ)\n\n15. **Hot Wallet App Testing**:\n\n Community members were urged to test hot wallet applications via a provided link. Additionally, discussions revolved around account on-ramping and integration with other platforms like PotLock. 👉 [Hot Wallet App Test Link](https://t.me/herewalletbot/app?startapp=web-app-potlock-org)\n\n16. **Discussion on RPC Selection in Apps**:\n\n Developers engaged in a detailed discussion about the integration of RPC (Remote Procedure Call) selection within applications for better user experience. Various ideas were exchanged, including load balancing, automatic selection of less loaded RPCs, and considerations for free vs. paid RPC services. Links to relevant RPC providers were shared for reference. 👉[Near RPC Providers](https://docs.near.org/api/rpc/providers)\n\n17. **Waitlist for NEAR Support on Coinbase Wallet**:\n\n A community member shared their involvement in the waitlist for NEAR support on Coinbase Wallet, emphasizing the importance of NEAR compatibility in the evolving multichain landscape.\n\n18. **Nodies for RPC Access**:\n\n Nodies, a platform offering both pruned and archival data, was suggested for RPC access consideration. Performance benchmarks and documentation links were provided for further exploration. 👉 [Nodies Platform](https://www.nodies.app/) |\n [Nodies Performance Benchmarks](https://docs.nodies.app/performance-benchmarks/benchmark-standard)\n\n19. **Issues with Testnet Support in Wallets**:\n\n Concerns were raised regarding the lack of testnet support in Here Wallet and Meteor Wallet. Community members requested assistance from the respective development teams to address the issue.\n\n20. **Technical Debt in MyNearWallet**:\n\n A developer from the Meteor Wallet team acknowledged the technical debt in MyNearWallet, explaining the high number of RPC requests per account due to tight coupling with the Wallet class. Plans to refactor and decouple code were discussed to mitigate this issue.\n\n21. **Pagoda** : \n\n- Improved QueryAPI logging system and DB connection pooling resulting in ~2-10 times better indexing performance.\n- KitWallet has been migrated to use QueryAPI for Access Keys indexer, making it more reliable for wallets that still use KitWallet.\n- QueryAPI hit all-time-high of 1.05M requests on April 26th, peaking at 400 req/second with ~250ms 95th percentile and ~15ms median GraphQL response time.\n\n22. **NEAR's Instant Resharding with Nightshade v2's Stateless Validation** : Check what NEAR's Cofounder **illia** has to say about Instant resharding with Nightshade v2's Stateless Validation. Click 👉 [here](https://twitter.com/ilblackdragon/status/1785979116396667269)\n\n  \n### THIS WEEKS TIPS 💡\n\n`Tip`: **Contract Deployment Issue Troubleshooting:**\n Developers encountering issues with contract deployment to temporary dev accounts after running `yarn deploy` are advised to ensure the correct syntax and configuration are used. Double-checking the account existence and ensuring proper contract compilation are recommended steps. \n\n`Tip`: **Client-Side Result Retrieval Challenge:**\n Developers facing challenges with obtaining contract call results on the client side, particularly when using callbacks via `NearPromise.then()`, are encouraged to verify contract method execution, inspect client-side code for promise handling, and debug with logging. \n  \n\n`Tip`: **New to NEAR? 👨‍💻 :** Whether you're familiar with Rust , JS, or simply eager to contribute to NEAR tooling, begin your journey with comprehensive NEAR docs and DevHub resources 👇:\n\n1. NEAR docs: [Link](https://docs.near.org/)\n2. DevHub: [Link](https://neardevhub.org/)\n3. Engage with NEAR Tools 👉[here](https://near.social/devhub.near/widget/app?page=blog&id=2496)\n4. Join the Community: Have questions? Join the lively discussions in [neardev](https://t.me/neardev) Telegram group.\n5. Office Hours: Get personalized assistance during our [DevHub Office Hours](https://near.social/devhub.near/widget/app?page=community&handle=devrel&tab=office-hours).\n\n\n### DEVELOPER OPPORTUNITIES \n\n- 🏆 **NEAR Bounty Booster Program Announcement:** 🏆\nThe NEAR Bounty Booster initiative has been launched to support hackers who use the NEAR stack in non-sponsored hackathons. By matching winnings up to $5,000, the program. The program is applicable to both Web2 and Web3 Hackathons ⭐️\n[Learn more](https://near.social/devhub.near/widget/app?page=blog&id=3021)\n\n- Feature your project in our weekly newsletter by checking out this page https://near.social/devhub.near/widget/app?page=community&handle=neardevnews&tab=how-to-get-featured\n\n- NEAR Horizon 2 Cohort invites developers like you to step into scaling decentralized applications. More details 👉[here](https://twitter.com/nearhorizon/status/1768310840120189123).\n\n- We've initiated alpha testing the BOS web engine for creating decentralized front end components on NEAR. Get involved today by following this [link](https://bwe-docs.near.dev/).\n\n\n  \n### RECENTLY UPDATED NEP'S ✅\n\n**APPROVED NEPs**: \n\nA successful NEP is one that addresses a specific problem or needs within the NEAR ecosystem. These are the NEPs that were approved by the protocol workgroup this week:\n\n- [NEP-519: Support for yielded execution](https://github.com/near/NEPs/pull/519) - Protocol Update \n- [NEP-491: Non-Refunable Storage](https://github.com/near/NEPs/pull/491) - Protocol Update\n- [NEP-330: Build details extension](https://github.com/near/NEPs/pull/533) - Contract standards Update \n- [NEP-536: Reduce the number of refund receipts](https://github.com/near/NEPs/pull/536) - Protocol Update\n  \n\n**REJECTED NEPs**:\n\n- [NEP-540: Reduce storage staking price by 10x](https://github.com/near/NEPs/issues/540) - Protocol Update\n\n\nTo learn more about NEP's click 👉 [here](https://github.com/near/NEPs/blob/master/neps/nep-0001.md) \nTo view all the NEP's click 👉 [here](https://github.com/orgs/near/projects/51/views/1)\n\n\n\n\n  \n### HACKS OF THE WEEK 👨‍💻🏆\n\n- [2FA](https://taikai.network/cryptocanal/hackathons/ethdam2024/projects/cluz0xnnj013uz301nfa9uj4g/idea) - A two-factor authentication multisig wallet that allows one to send tokens and mint NFTs on multiple networks. \"FA had a great UX, exciting implementation of chain signatures and proper use case.\n\n- [Feedback](https://taikai.network/cryptocanal/hackathons/ethdam2024/projects/cluyuw0j200y3yz01yjjd4rap/idea) - A privacy-preserving B2C survey platform that creates a NEAR account from a participant's phone number used to derive an Ethereum Account and submit a cross-chain private vote. Amazing integration with survey phone calls and blockchain, great potential.\n\n  \n### CHAIN ABSTRACTION COMMUNITY 🤩\n\n**The Chain Abstraction** community hosted the first Chain Abstraction Community Call on the 25th of April 2024! Highlights included a demo on minting NFTs on Ethereum from NEAR accounts, discussions on EVM support integration, and presentations from ETH DAM chain signature bounty winners. These calls will be monthly, and discussions continue in the Telegram channel.\n\n- Watch the recap [here](https://near.social/devhub.near/widget/app?page=community&handle=chain-abstraction&tab=community-calls)\n- Check out more details about the call [here](https://www.youtube.com/watch?v=9RSt7vPR-yM)\n\n\n\n  \n# UPCOMING EVENTS \n\n\n### ONLINE:\n- Thursdays 5PM UTC | **Join us on DevHub Livestreams Hosted by Joe** | [Live on X](https://twitter.com/NEARDevHub) and [Twitch](https://twitch.tv/neardevhub)\n- May 14th 2024 | Tools Community Call Hosted by Lyudmil | [Add to your calendar»](https://calendar.google.com/calendar/u/0/r/eventedit/copy/MXY3bnFxZDFnM21yNTFqZmc1ZzJtaWI4dnVfMjAyNDA1MTRUMTcwMDAwWiBjX2Y1NGVkMzdmZDkyMzI3YWNkYzdlNDM0M2ZlNDA3MjJhZTU3OTdiNmM4MjkyOWJhOTNlOWYzYTg5YzY5NjU3YWJAZw)\n- May 15th 2024 | Documentation community call | [Add to your calendar»](https://calendar.google.com/calendar/u/0/r/eventedit/copy/NjhpcWZjN20yaGxvdnMzdjg2Mm45MGdtYWRfMjAyNDA1MTVUMTcwMDAwWiBjX2Y1NGVkMzdmZDkyMzI3YWNkYzdlNDM0M2ZlNDA3MjJhZTU3OTdiNmM4MjkyOWJhOTNlOWYzYTg5YzY5NjU3YWJAZw)\n\n### USA:\n\n- May 29 - 31, 2024 | Consensus | [Coindesk](https://www.coindesk.com/events/consensus-2024) | NEAR Foundation\n- April 29 - May 3, 2024 | [5th Annual International Tech Summit](https://www.internationaltechsummit.com/) | Hamilton, Bermuda | Penrose | \"Abhi V / Olga Chris D / Abhi speaking\"\n\n### EUROPE:\n\n- May 8-9, 2024 | Crypto and Digital Assets Summit \n- May 21-23, 2024 | London Blockchain Conference \n- May 24, 2024 | ETHBerlin | [DoD (dept. of decentralization)](https://ethberlin.com/) | DevHub, NEARWEEK\n- May 27-30, 2024 | Blocksplit | [Eco Balkans Calimero](https://blocksplit.org/) \n\n31, 2024 | Blockchance 2024 | [Blockchance](https://www.blockchance.eu/) | Eco\n- July 8-11, 2024 | ETHCC | Bettina/Jerome \"Ethereum France\" | NEAR Foundation (Summit + Sponsorship)\n- July 11, 2024 | Pragma Brussels | [ETHGlobal](https://www.ethglobal.co/) | NEAR Foundation\n- July 12 – 14, 2024 | ETHGlobal Brussels | [ETHGlobal](https://www.ethglobal.co/) | DevHub\n\n\n\n  \nIf you are running a Local NEAR event please register as a Hackbox host 👉 [here](https://near.org/hackbox.near/widget/home). \n\n  \n## CONSENSUS 2024\nExciting opportunities await those interested in participating in the upcoming Consensus event. Choose from three ticket options tailored for the NEAR Ecosystem:\n\n- Hackathon Developer Pass: For active developers and open-source contributors committed to participating in-person at the EasyA Consensus Hackathon on May 29-31, A complimentary Developer Pass is offered to approved applicants until capacity is reached. Apply 👉[here](https://consensus2024.coindesk.com/apply/developer-hackathon/-id/0).\n\n- Developer Pass: Special $109 rate available for active Web3 and Web2 developers. Apply before prices increase on March 15th [here](https://consensus2024.coindesk.com/apply/developer/-id/0). The Developer Pass grants access to all three days of Consensus on May 29-31. \n\n- 15% off Pro Passes and Explorer Passes: Enjoy a 15% discount on Pro Passes and Explorer Passes using the code \"NEAR\" [here](https://consensus2024.coindesk.com/register?promo=NEAR).\n\n\n  \n## JOIN COMMUNITIES - TG CHANNELS \n- [Protocol Community](https://t.me/NEAR_Protocol_Community_Group)\n- [Stake-wars](https://t.me/near_stake_wars)\n- [Tools Community](https://t.me/NEAR_Tools_Community_Group)\n- [ZK Community](https://t.me/NearZeroKnowledge)\n- [Documentation Community](https://t.me/neardocscg)\n- [Wallet Builders](https://nearbuilders.com/tg-wallet)\n- [Contracts Community](https://t.me/nearnft)\n- [NEAR Devs](https://t.me/neardev)\n- [Jutsu and BOS questions](https://t.me/tryjutsu/973)\n\n  \n###### NEAR Dev NEWS is curated by the NEAR Dev NEWS group, and maintained by @victorkanu1.near & @orangejoe.near \n\n  \n\n\n\n##### Thanks for reading, See you Next Week!\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n", "metadata": { "title": "NEAR Dev NEWS #10", "createdAt": "2024-05-03", "updatedAt": "2024-05-03", "publishedAt": "2024-05-03", "status": "DRAFT", "subtitle": "Milestone edition [Bounty Boost Program]", "description": "Milestone edition [Bounty Boost Program]", "author": "victorkanu1.near", "id": "3232", "category": "news", "communityAddonId": "blogv2" } } } } } }