Search
Search

Transaction: F1CUcxe...pDcT

Receiver
Status
Succeeded
Transaction Fee
0.00194 
Deposit Value
0 
Gas Used
19 Tgas
Attached Gas
100 Tgas
Created
June 05, 2024 at 8:36:14pm
Hash
F1CUcxeLsrFpoXjd2TEF7qqqd2tjPDBSvPeRZDwnpDcT

Actions

Called method: 'set_community_socialdb' in contract: devhub.near
Arguments:
{ "handle": "neardevnews", "data": { "blog": { "-near-dev-news-7-3235": { "": "\nWelcome to NEAR Dev NEWS, your prime source for the latest in the NEAR Developer ecosystem! NEAR lays the groundwork for all blockchain apps, offering an open-source system empowering devs to create fully decentralized, interoperable apps. Our Digest showcases developer progress and technical updates shaping the blockchain OS.\n\nIn this edition, we'll be exploring a plethora of updates and activities set out for the week, designed to keep you engaged with developers within the NEAR community. \n\n  \n### FEATURED RELEASES & PR's 🤩\n\n- **NEAR Rust SDK 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- `nearcore` **Version 1.39.0 has been released** this week and function call base cost is reduced. For small transactions like on [Cosmose](https://twitter.com/Cosmose_) and [hotdao](https://twitter.com/hotdao_), it is a 2x reduction in cost and 2x in throughput. RPC is now faster! Learn more 👉 [here](https://github.com/near/nearcore/releases)\n\n- `near-api-js` **Version 4.0.0 has been released**. It contains:\n\n👉 More than 36% bundle size reduction (from 380kb to 240kb). Info 👉[here](https://bundlephobia.com/package/near-api-js@4.0.0)\n👉 Failover RPC configuration\n👉 Executing view functions without the need of a Connection object and more!\n👉 You can read more about the changes 👉 [here](https://github.com/near/near-api-js/pull/1318)!\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  \n### DEVELOPER UPDATES 🛠\n\n- Users discussed tutorials for creating a bot to monitor transactions on the NEAR blockchain. Check out [NEAR Lake Framework Documentation](https://docs.near.org/concepts/advanced/near-lake-framework). It leverages pikespeak.ai 👉 [here](https://t.me/nearwatchbot). You can also check out [this repository](https://github.com/k-o-l-e-s/LNC-NEAR-watcher), a simple bot to get notified about TX's on NEAR's Mainnet.\n\n- Developers engaged in discussions about the possibility of NEAR's capability to sign Secp256k signatures for NFC chips. \n\n- Fast NEAR announces the new NEAR Data server! It's a simple and free alternative to the NEAR Lake Framework for data indexing. Click 👉 [here](https://twitter.com/fast_near/status/1777814928646197417) to learn more.\n\n- Developers discussed the validity period of signed transactions and the possibility of migrating contract state. They explored the technical aspects of transaction validity and contract state migration within the NEAR blockchain ecosystem.\n\n- Catch up on the recording of our live event with Hacken discussing WASM code coverage 👉 [here](https://twitter.com/i/spaces/1MYxNoAjnAXKw/peek?s=20).\n\n- NEAR Foundation Launches Infrastructure Committee with $4 Million in Funding. Learn more 👉 [here](https://pages.near.org/blog/near-launches-infrastructure-committee/)\n\n- A developer encountered a technical issue while attempting to broadcast a transaction on Ref with MNW, resulting in an error message. Discussions focused on diagnosing the cause of the issue, including potential reasons such as network connectivity problems or RPC issues.\n\n- Looking for a production ready rust contract made on `near-sdk` 5.1.0? Reference DevHub’s contract 👉 [here](https://github.com/NEAR-DevHub/neardevhub-contract).\n\n- Mark your calendar, starting this Thursday, DevHub will be streaming LIVE & unedited! Each week we will have guests to talk development, teach technical concepts, dev news, code reviews, and more. [Live on X](https://twitter.com/NEARDevHub) and [Twitch](https://twitch.tv/neardevhub). \n\n- Pagoda releases Chain Signatures that simplify user experiences by enabling users multichain access without leaving their NEAR account, unlocking billions of dollars in previously inaccessible liquidity.\n\n- Community members inquire about retrieving the epoch start block height via RPC. Ecosystem Devs suggests accessing it through the validators RPC endpoint, which you can find 👉 [here](https://docs.near.org/api/rpc/network#validation-status).\n\n- Seeking documentation about MultiSig on NEAR. Check out the MultiSig contract repository 👉 [here](https://github.com/near/core-contracts/tree/master/multisig).\n\n- Proximity labs shares Ideas for building with chain signatures 👉 [here](https://twitter.com/proximityfi/status/1774723437032038408?t=Y_oem9i384uPvwRIZKOuiw&s=35).\n\n- Developers requested a demo/tutorial for testing substream setup for NEAR blockchain.\n\n- User inquired about the availability of a no-std NEAR SDK. A link to nesdie repository was shared. 👉 [nesdie GitHub repository](https://github.com/austinabell/nesdie/).\n\n- Users discussed the challenges of retrieving token metadata, particularly for FTs, through various APIs. Suggestions for potential APIs were mentioned, such as [Fast NEAR](https://twitter.com/fast_near/status/1773398764859847008?t=9a8M8CwJqNBxNcW1p2d8DA&s=19) and [Pikespeak](https://doc.pikespeak.ai/).\n\n- Tools Community call and DevHub Livestream recordings are now available on [DevHub's Youtube](https://www.youtube.com/@NEARDevHub)\n\n- Developers provided an update on the signMessage issue and shared the latest developments on [GitHub](https://github.com/near/near-wallet/issues/3135).\n\n- Login functionality is being migrated to the wallet selector.\n\n- Developers discussed the challenges with wallet integration and offline signing standards. They referenced an [issue on GitHub](https://github.com/near/wallet-selector/issues/405) related to this topic.\n\n- The Protocol Work Group prepares to vote on NEP-536, a proposal to optimize NEAR protocol's performance. NEP-536 focuses on reducing the number of refund receipts, a significant contributor to runtime overhead. Don't miss this opportunity to contribute to the discussion 👉 [here](https://github.com/near/NEPs/pull/536).\n\n- Developers offered assistance on deleting a wallet and provided instructions on using a specific tool for the process. [Tool Link](https://lantstool.io/).\n\n- Developers Discussed changes in the Gas struct and its usage, particularly emphasizing the transition from manipulating raw integers to using dedicated constructors like `Gas::from_tgas()`. [Gas Struct Documentation](https://docs.rs/near-sdk/latest/near_sdk/struct.Gas.html).\n\n- Discussions continued on the handling of promises in code implementations, specifically regarding their execution and impact on transaction returns. Various considerations were raised regarding serialization and atomicity in NEAR Protocol transactions.\n\n- [NEAR protocol 2024 roadmap update](https://near.org/blog/near-q4-protocol-roadmap-update).\n\n- Jutsu.ai expressing interest in collaborating to onboard web2 developers to web3.\n\n\n  \n### THIS WEEKS TIPS 💡\n\n- `Tip`: A request was made to report broken links. The suggestion was to open an issue on the docs GitHub or make a PR with the proper link. The relevant link for documentation issues is 👉 [here](https://docs.github.com/).\n\n- `Tip`: Need to top-up USDT to a NEAR wallet on the test network? Use a faucet. [Faucet Link](https://near-faucet.io/).\n\n- `Tip`: Need help checking whether a NEAR account ID exists or not? Use the fetch API available via BOS to make an RPC query call to get account information.\n\n- `Tip` List of all the current NEAR Stakers: https://near-staking.com\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### 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 | **8th March 2024**\n- [NEP-491: Non-Refunable Storage](https://github.com/near/NEPs/pull/491) - Protocol Update | **26th Feb 2024**\n  \n\n**REVIEW STAGE**:\n\nSubject matter experts are currently reviewing the following NEPs. Some of the working group members are also deciding whether to accept or reject them. Feel free to explore, these NEPs will aid you during your development as you integrate them with your dApps. Share your thoughts and leave a comment.\n\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\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### ETHDam 🏆\n\nAt the ETHDam Hackathon, you can engage with NEAR's ecosystem through various avenues. Joining the event's chat allows for networking ([ETHDam Hackathon chat](https://t.me/+l1hv9RxZCCVkNzA0)), while Owen offers on-site support. NEAR's bounty program provides lucrative opportunities, including the [Chain Signatures](https://linktr.ee/chainsignatures) bounty offering $3,000 in USDC for innovative use cases of the Chain Signatures API, and the \"Power your startup with NEAR\" bounty, also with a $3,000 prize, for integrating startups with NEAR's technology stack. \n\nCriteria for submissions and judging prioritize creativity, quality, and technical excellence, with resources like [NEAR Components](https://docs.near.org/build/near-components/what-is) and [NEAR testnet faucets](https://near-faucet.io/) available for support. By engaging with NEAR, developers can explore cutting-edge technologies and compete for substantial prizes at the hackathon.\n\n\n  \n### HACKS OF THE WEEK 👨‍💻🏆\n\n- Check out the RPC Selector browser extension for NEAR, allowing you to customize RPC endpoints for dapps and wallets: [GitHub - RPC Selector](https://github.com/Sliman4/rpc-selector)\n\n**Building something on NEAR?** Share your project with the community! Tell us about it in the documentation community group, and get featured. Click 👉 [here](https://t.me/neardocscg).\n\n\n\n  \n### STAKEWARS 🚀\n**Participating in Stakewars? Here are some quick news and notes you should be aware of.**\n\n- The community announced the temporary suspension of operations on StatelessNet due to challenges in meeting required standards. This decision aims to ensure a more stable experience for all participants.\n\n- The Stake Wars IV program concluded, with plans to potentially restart the program in the future. Participants were thanked for their participation in the event.\n\n- As long as you are qualified for the reward program details we shared and followed the step to onboard with StatelessNet, you should get a reward.\n\n- The team plans to finalize reward distribution and send rewards by the end of this week. Rewards for validators will be sent to the owner ID of the staking pool contract on mainnet, as provided during registration.\n\n- When we resume StatelessNet, the network may start from a fresh state, requiring major updates. Keeping nodes up during this period may not be beneficial.\n\n- We'll inform the community once we start accepting proposals for the traffic generation program again.\n\n- There's a possibility of restarting the program later. We'll keep you updated on any developments. Thank you all for participating in Stake Wars IV!\n\n\n\n\n  \n### CHAIN ABSTRACTION COMMUNITY 🤩\n\nThe chain abstraction community has been actively engaged in discussions and developments aimed at enhancing interoperability and standardization across different blockchain networks.They have been exploring techniques like Multi-Party Computation (MPC) to address security and key management concerns. Discussions around key rotation within MPC systems have been gaining traction, as highlighted in recent community exchanges. As part of ongoing efforts to streamline development practices, there have been discussions on standardized deployment data storage practices, with community members advocating for transparent and accessible repositories of contract deployment information. \n\nCheck out this 👉 [GitHub repository](https://github.com/near/mpc-recovery) containing code for MPC contracts, illustrating the implementation of payload-based key management for chain signature requests and responses.\n\nFor further details, you can refer to the following links:\n\n👉 [Chain Signatures Documentation](https://docs.near.org/concepts/abstraction/chain-signatures)\n👉 [NEAR Multichain Example](https://github.com/near-examples/near-multichain)\n👉 [Chain Signatures Use Cases](https://docs.near.org/concepts/abstraction/signatures/use-cases)\n👉 [FastAuth SDK Documentation](https://docs.near.org/tools/fastauth-sdk)\n👉 [NEAR NFT Minting on Farcaster](https://warpcast.com/brower1/0xab61fd1b)\n\n[Learn more about the Chain Abstraction Community](https://near.social/devhub.near/widget/app?page=community&handle=chain-abstraction)\n\n\n  \n### CALL FOR CONTRIBUTORS 📞\n\n- Ecosystem developers propose a devcontainer image for examples encompassing both Rust and Node tooling. Volunteers are welcomed to contribute to `near-devcontainers` and test the additional container on examples. [Join Tools Community](https://t.me/NEAR_Tools_Community_Group)\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- 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- With the upcoming SDK 5.1 release, there will be updates needed in transitioning from #[near_bindgen] to #[near]. Matias is working on documentation updates, but additional assistance may be required. Don't hesitate to reach out if you can lend a hand! Reach out to [Docs community](https://t.me/neardocscg).\n\n- Given the release of the new SDK, both docs and example repositories need updating. If you want to contribute , [join the Docs Community Group](https://near.social/devgovgigs.near/widget/gigs-board.pages.community.activity?handle=documentation).\n\n- Check out [DevHub's On-Chain Quests](https://near.social/devhub.near/widget/app?page=community&handle=challenges) ⛳️, where you'll find a dynamic array of challenges across various communities, earning recognition and respect as you conquer each one! \n\n\n  \n# UPCOMING EVENTS \n\n\n### ONLINE:\n- April 18, 2024 | Contract Standards WG Call #5 | [Add to your calendar](https://bit.ly/3UcYyfW)\n- April 17 | Documentation community call | [Add to your Calendar](https://calendar.google.com/calendar/u/0/r/eventedit/copy/NjhpcWZjN20yaGxvdnMzdjg2Mm45MGdtYWRfMjAyNDA0MTdUMTcwMDAwWiBjX2Y1NGVkMzdmZDkyMzI3YWNkYzdlNDM0M2ZlNDA3MjJhZTU3OTdiNmM4MjkyOWJhOTNlOWYzYTg5YzY5NjU3YWJAZw)\n- Chain Abstraction Community Call | Coming soon \n- Thursdays 5PM UTC | **DevHub Livestreams** | [Live on X](https://twitter.com/NEARDevHub) and [Twitch](https://twitch.tv/neardevhub)\n\n### ASIA:\n\n- March 26, 2024 - March 27, 2024 | WOW Summit | Hong Kong \n- March 27, 2024 - March 28, 2024 | [BUIDL Asia | Seoul, Korea](https://www.buidl.asia/) | KryptoSeoul 👉 NEAR Foundation and Korea Hub will be present at the event \n- March 29, 2024 - March 31, 2024 | [ETH Seoul | Seoul, Korea](http://www.ethseoul.org/) | KryptoSeoul, Dystopia Labs 👉 DevHub and NEARWEEK will be present at the event \n- April 6-9, 2024 | Hong Kong Web3 Festival 2024 | Hong Kong | HashKey and Wanxiang | BD to speak\n\n### MIDDLE EAST\n- April 15-16, 2024 | [Blockchain Life 2024](https://blockchain-life.com/asia/en/spring2024/?utm_source=google&utm_medium=organic) | Dubai | Blockchain Life | NEAR Foundation, Arpit has a speaker slot\n- April 18-19, 2024 | [Token 2049 Dubai](https://www.dubai.token2049.com/) | Dubai | | NEAR Foundation organizing booth. Illia, Chris speaking\n- April 22-23, 2024 | World Blockchain Summit 2024 | Dubai | Trescon | NEAR Foundation, tentative speaker slot for Arpit\n\n### EUROPE\n\n- March 23, 2024 - March 24, 2024 | [Money Motion 2024](https://moneymotion.com/) | Zagreb, Croatia | Money Motion\n- March 27, 2024 - March 30, 2024 | [ETH Bucharest | Bucharest, Romania](https://www.ethbucharest.xyz/) | ETH Bucharest 👉 DevHub will be present at the event \n- March 18, 2024 - March 20, 2024 | [Digital Asset Summit](https://www.blockworks.co/) | London | Blockworks\n- April 8-12, 2024 | [Paris Blockchain Week](https://www.parisblockchainweek.com/) | Paris, France | | NF leading; Chris D speaking\nApril 12-14, 2024 | [ETHDam](https://www.ethdam.com/) | Amsterdam, Netherlands | ETHDam | DevHub\n\n### SOUTH AMERICA\n\n- March 22nd - March 24 | [ETHSamba](https://ethsamba.org/) | Brazil 👉 DevHub DevRels / NEAR Campus will be present at the event\n\n### THE UNITED STATES \n\n- March 20, 2024 - March 22, 2024 | IWB 2024 | DC area\n- April 3-5, 2024 | [NFT.NYC](https://www.nft.nyc/) | New York, NY | NFT.NYC\n- April | San Francisco | Funding the Commons (AI Focused Day) | FtheC | Banyan + EDGE\n- April 18-19, 2024 | The Institutional Crypto Conference East | New York, NY \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\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### Quote of the week: \n\n**Efte** from tools community: \"I Just wanna give a big shoutout to Lyudmil (DevHub DevRel) who has just spent multiple hours explaining the ins and outs of a fungible token contract with me. I am sure I will now not only be able to interact and create those, but also have a better overview of what sources to go to whenever I am stuck with other examples. I will put this to the test soon by creating contracts interacting with the ft contracts on different levels.\"\n\n  \n###### NEAR Dev NEWS is curated by the NEAR Dev NEWS group , and maintained by @victorkanu1.near & @orangejoe.near \n\n  \n![Sample Image](https://i.ibb.co/MDJ5zZn/2024-04-03-16-10-19.jpg)\n\n\n\n\n\n\n\n##### Thanks for reading, See you Next Week!", "metadata": { "title": " NEAR Dev NEWS #7", "createdAt": "2024-04-11", "updatedAt": "2024-04-11", "publishedAt": "2024-04-11", "status": "DRAFT", "subtitle": "Engage with NEAR", "description": "Engage with NEAR", "author": "victorkanu1.near", "id": "3235", "category": "news", "communityAddonId": "blogv2" } } } } }

Transaction Execution Plan

Convert Transaction To Receipt
Gas Burned:
355 Ggas
Tokens Burned:
0.00004 
Receipt:
Predecessor ID:
Receiver ID:
Gas Burned:
5 Tgas
Tokens Burned:
0.00058 
Called method: 'set_community_socialdb' in contract: devhub.near
Arguments:
{ "handle": "neardevnews", "data": { "blog": { "-near-dev-news-7-3235": { "": "\nWelcome to NEAR Dev NEWS, your prime source for the latest in the NEAR Developer ecosystem! NEAR lays the groundwork for all blockchain apps, offering an open-source system empowering devs to create fully decentralized, interoperable apps. Our Digest showcases developer progress and technical updates shaping the blockchain OS.\n\nIn this edition, we'll be exploring a plethora of updates and activities set out for the week, designed to keep you engaged with developers within the NEAR community. \n\n  \n### FEATURED RELEASES & PR's 🤩\n\n- **NEAR Rust SDK 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- `nearcore` **Version 1.39.0 has been released** this week and function call base cost is reduced. For small transactions like on [Cosmose](https://twitter.com/Cosmose_) and [hotdao](https://twitter.com/hotdao_), it is a 2x reduction in cost and 2x in throughput. RPC is now faster! Learn more 👉 [here](https://github.com/near/nearcore/releases)\n\n- `near-api-js` **Version 4.0.0 has been released**. It contains:\n\n👉 More than 36% bundle size reduction (from 380kb to 240kb). Info 👉[here](https://bundlephobia.com/package/near-api-js@4.0.0)\n👉 Failover RPC configuration\n👉 Executing view functions without the need of a Connection object and more!\n👉 You can read more about the changes 👉 [here](https://github.com/near/near-api-js/pull/1318)!\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  \n### DEVELOPER UPDATES 🛠\n\n- Users discussed tutorials for creating a bot to monitor transactions on the NEAR blockchain. Check out [NEAR Lake Framework Documentation](https://docs.near.org/concepts/advanced/near-lake-framework). It leverages pikespeak.ai 👉 [here](https://t.me/nearwatchbot). You can also check out [this repository](https://github.com/k-o-l-e-s/LNC-NEAR-watcher), a simple bot to get notified about TX's on NEAR's Mainnet.\n\n- Developers engaged in discussions about the possibility of NEAR's capability to sign Secp256k signatures for NFC chips. \n\n- Fast NEAR announces the new NEAR Data server! It's a simple and free alternative to the NEAR Lake Framework for data indexing. Click 👉 [here](https://twitter.com/fast_near/status/1777814928646197417) to learn more.\n\n- Developers discussed the validity period of signed transactions and the possibility of migrating contract state. They explored the technical aspects of transaction validity and contract state migration within the NEAR blockchain ecosystem.\n\n- Catch up on the recording of our live event with Hacken discussing WASM code coverage 👉 [here](https://twitter.com/i/spaces/1MYxNoAjnAXKw/peek?s=20).\n\n- NEAR Foundation Launches Infrastructure Committee with $4 Million in Funding. Learn more 👉 [here](https://pages.near.org/blog/near-launches-infrastructure-committee/)\n\n- A developer encountered a technical issue while attempting to broadcast a transaction on Ref with MNW, resulting in an error message. Discussions focused on diagnosing the cause of the issue, including potential reasons such as network connectivity problems or RPC issues.\n\n- Looking for a production ready rust contract made on `near-sdk` 5.1.0? Reference DevHub’s contract 👉 [here](https://github.com/NEAR-DevHub/neardevhub-contract).\n\n- Mark your calendar, starting this Thursday, DevHub will be streaming LIVE & unedited! Each week we will have guests to talk development, teach technical concepts, dev news, code reviews, and more. [Live on X](https://twitter.com/NEARDevHub) and [Twitch](https://twitch.tv/neardevhub). \n\n- Pagoda releases Chain Signatures that simplify user experiences by enabling users multichain access without leaving their NEAR account, unlocking billions of dollars in previously inaccessible liquidity.\n\n- Community members inquire about retrieving the epoch start block height via RPC. Ecosystem Devs suggests accessing it through the validators RPC endpoint, which you can find 👉 [here](https://docs.near.org/api/rpc/network#validation-status).\n\n- Seeking documentation about MultiSig on NEAR. Check out the MultiSig contract repository 👉 [here](https://github.com/near/core-contracts/tree/master/multisig).\n\n- Proximity labs shares Ideas for building with chain signatures 👉 [here](https://twitter.com/proximityfi/status/1774723437032038408?t=Y_oem9i384uPvwRIZKOuiw&s=35).\n\n- Developers requested a demo/tutorial for testing substream setup for NEAR blockchain.\n\n- User inquired about the availability of a no-std NEAR SDK. A link to nesdie repository was shared. 👉 [nesdie GitHub repository](https://github.com/austinabell/nesdie/).\n\n- Users discussed the challenges of retrieving token metadata, particularly for FTs, through various APIs. Suggestions for potential APIs were mentioned, such as [Fast NEAR](https://twitter.com/fast_near/status/1773398764859847008?t=9a8M8CwJqNBxNcW1p2d8DA&s=19) and [Pikespeak](https://doc.pikespeak.ai/).\n\n- Tools Community call and DevHub Livestream recordings are now available on [DevHub's Youtube](https://www.youtube.com/@NEARDevHub)\n\n- Developers provided an update on the signMessage issue and shared the latest developments on [GitHub](https://github.com/near/near-wallet/issues/3135).\n\n- Login functionality is being migrated to the wallet selector.\n\n- Developers discussed the challenges with wallet integration and offline signing standards. They referenced an [issue on GitHub](https://github.com/near/wallet-selector/issues/405) related to this topic.\n\n- The Protocol Work Group prepares to vote on NEP-536, a proposal to optimize NEAR protocol's performance. NEP-536 focuses on reducing the number of refund receipts, a significant contributor to runtime overhead. Don't miss this opportunity to contribute to the discussion 👉 [here](https://github.com/near/NEPs/pull/536).\n\n- Developers offered assistance on deleting a wallet and provided instructions on using a specific tool for the process. [Tool Link](https://lantstool.io/).\n\n- Developers Discussed changes in the Gas struct and its usage, particularly emphasizing the transition from manipulating raw integers to using dedicated constructors like `Gas::from_tgas()`. [Gas Struct Documentation](https://docs.rs/near-sdk/latest/near_sdk/struct.Gas.html).\n\n- Discussions continued on the handling of promises in code implementations, specifically regarding their execution and impact on transaction returns. Various considerations were raised regarding serialization and atomicity in NEAR Protocol transactions.\n\n- [NEAR protocol 2024 roadmap update](https://near.org/blog/near-q4-protocol-roadmap-update).\n\n- Jutsu.ai expressing interest in collaborating to onboard web2 developers to web3.\n\n\n  \n### THIS WEEKS TIPS 💡\n\n- `Tip`: A request was made to report broken links. The suggestion was to open an issue on the docs GitHub or make a PR with the proper link. The relevant link for documentation issues is 👉 [here](https://docs.github.com/).\n\n- `Tip`: Need to top-up USDT to a NEAR wallet on the test network? Use a faucet. [Faucet Link](https://near-faucet.io/).\n\n- `Tip`: Need help checking whether a NEAR account ID exists or not? Use the fetch API available via BOS to make an RPC query call to get account information.\n\n- `Tip` List of all the current NEAR Stakers: https://near-staking.com\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### 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 | **8th March 2024**\n- [NEP-491: Non-Refunable Storage](https://github.com/near/NEPs/pull/491) - Protocol Update | **26th Feb 2024**\n  \n\n**REVIEW STAGE**:\n\nSubject matter experts are currently reviewing the following NEPs. Some of the working group members are also deciding whether to accept or reject them. Feel free to explore, these NEPs will aid you during your development as you integrate them with your dApps. Share your thoughts and leave a comment.\n\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\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### ETHDam 🏆\n\nAt the ETHDam Hackathon, you can engage with NEAR's ecosystem through various avenues. Joining the event's chat allows for networking ([ETHDam Hackathon chat](https://t.me/+l1hv9RxZCCVkNzA0)), while Owen offers on-site support. NEAR's bounty program provides lucrative opportunities, including the [Chain Signatures](https://linktr.ee/chainsignatures) bounty offering $3,000 in USDC for innovative use cases of the Chain Signatures API, and the \"Power your startup with NEAR\" bounty, also with a $3,000 prize, for integrating startups with NEAR's technology stack. \n\nCriteria for submissions and judging prioritize creativity, quality, and technical excellence, with resources like [NEAR Components](https://docs.near.org/build/near-components/what-is) and [NEAR testnet faucets](https://near-faucet.io/) available for support. By engaging with NEAR, developers can explore cutting-edge technologies and compete for substantial prizes at the hackathon.\n\n\n  \n### HACKS OF THE WEEK 👨‍💻🏆\n\n- Check out the RPC Selector browser extension for NEAR, allowing you to customize RPC endpoints for dapps and wallets: [GitHub - RPC Selector](https://github.com/Sliman4/rpc-selector)\n\n**Building something on NEAR?** Share your project with the community! Tell us about it in the documentation community group, and get featured. Click 👉 [here](https://t.me/neardocscg).\n\n\n\n  \n### STAKEWARS 🚀\n**Participating in Stakewars? Here are some quick news and notes you should be aware of.**\n\n- The community announced the temporary suspension of operations on StatelessNet due to challenges in meeting required standards. This decision aims to ensure a more stable experience for all participants.\n\n- The Stake Wars IV program concluded, with plans to potentially restart the program in the future. Participants were thanked for their participation in the event.\n\n- As long as you are qualified for the reward program details we shared and followed the step to onboard with StatelessNet, you should get a reward.\n\n- The team plans to finalize reward distribution and send rewards by the end of this week. Rewards for validators will be sent to the owner ID of the staking pool contract on mainnet, as provided during registration.\n\n- When we resume StatelessNet, the network may start from a fresh state, requiring major updates. Keeping nodes up during this period may not be beneficial.\n\n- We'll inform the community once we start accepting proposals for the traffic generation program again.\n\n- There's a possibility of restarting the program later. We'll keep you updated on any developments. Thank you all for participating in Stake Wars IV!\n\n\n\n\n  \n### CHAIN ABSTRACTION COMMUNITY 🤩\n\nThe chain abstraction community has been actively engaged in discussions and developments aimed at enhancing interoperability and standardization across different blockchain networks.They have been exploring techniques like Multi-Party Computation (MPC) to address security and key management concerns. Discussions around key rotation within MPC systems have been gaining traction, as highlighted in recent community exchanges. As part of ongoing efforts to streamline development practices, there have been discussions on standardized deployment data storage practices, with community members advocating for transparent and accessible repositories of contract deployment information. \n\nCheck out this 👉 [GitHub repository](https://github.com/near/mpc-recovery) containing code for MPC contracts, illustrating the implementation of payload-based key management for chain signature requests and responses.\n\nFor further details, you can refer to the following links:\n\n👉 [Chain Signatures Documentation](https://docs.near.org/concepts/abstraction/chain-signatures)\n👉 [NEAR Multichain Example](https://github.com/near-examples/near-multichain)\n👉 [Chain Signatures Use Cases](https://docs.near.org/concepts/abstraction/signatures/use-cases)\n👉 [FastAuth SDK Documentation](https://docs.near.org/tools/fastauth-sdk)\n👉 [NEAR NFT Minting on Farcaster](https://warpcast.com/brower1/0xab61fd1b)\n\n[Learn more about the Chain Abstraction Community](https://near.social/devhub.near/widget/app?page=community&handle=chain-abstraction)\n\n\n  \n### CALL FOR CONTRIBUTORS 📞\n\n- Ecosystem developers propose a devcontainer image for examples encompassing both Rust and Node tooling. Volunteers are welcomed to contribute to `near-devcontainers` and test the additional container on examples. [Join Tools Community](https://t.me/NEAR_Tools_Community_Group)\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- 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- With the upcoming SDK 5.1 release, there will be updates needed in transitioning from #[near_bindgen] to #[near]. Matias is working on documentation updates, but additional assistance may be required. Don't hesitate to reach out if you can lend a hand! Reach out to [Docs community](https://t.me/neardocscg).\n\n- Given the release of the new SDK, both docs and example repositories need updating. If you want to contribute , [join the Docs Community Group](https://near.social/devgovgigs.near/widget/gigs-board.pages.community.activity?handle=documentation).\n\n- Check out [DevHub's On-Chain Quests](https://near.social/devhub.near/widget/app?page=community&handle=challenges) ⛳️, where you'll find a dynamic array of challenges across various communities, earning recognition and respect as you conquer each one! \n\n\n  \n# UPCOMING EVENTS \n\n\n### ONLINE:\n- April 18, 2024 | Contract Standards WG Call #5 | [Add to your calendar](https://bit.ly/3UcYyfW)\n- April 17 | Documentation community call | [Add to your Calendar](https://calendar.google.com/calendar/u/0/r/eventedit/copy/NjhpcWZjN20yaGxvdnMzdjg2Mm45MGdtYWRfMjAyNDA0MTdUMTcwMDAwWiBjX2Y1NGVkMzdmZDkyMzI3YWNkYzdlNDM0M2ZlNDA3MjJhZTU3OTdiNmM4MjkyOWJhOTNlOWYzYTg5YzY5NjU3YWJAZw)\n- Chain Abstraction Community Call | Coming soon \n- Thursdays 5PM UTC | **DevHub Livestreams** | [Live on X](https://twitter.com/NEARDevHub) and [Twitch](https://twitch.tv/neardevhub)\n\n### ASIA:\n\n- March 26, 2024 - March 27, 2024 | WOW Summit | Hong Kong \n- March 27, 2024 - March 28, 2024 | [BUIDL Asia | Seoul, Korea](https://www.buidl.asia/) | KryptoSeoul 👉 NEAR Foundation and Korea Hub will be present at the event \n- March 29, 2024 - March 31, 2024 | [ETH Seoul | Seoul, Korea](http://www.ethseoul.org/) | KryptoSeoul, Dystopia Labs 👉 DevHub and NEARWEEK will be present at the event \n- April 6-9, 2024 | Hong Kong Web3 Festival 2024 | Hong Kong | HashKey and Wanxiang | BD to speak\n\n### MIDDLE EAST\n- April 15-16, 2024 | [Blockchain Life 2024](https://blockchain-life.com/asia/en/spring2024/?utm_source=google&utm_medium=organic) | Dubai | Blockchain Life | NEAR Foundation, Arpit has a speaker slot\n- April 18-19, 2024 | [Token 2049 Dubai](https://www.dubai.token2049.com/) | Dubai | | NEAR Foundation organizing booth. Illia, Chris speaking\n- April 22-23, 2024 | World Blockchain Summit 2024 | Dubai | Trescon | NEAR Foundation, tentative speaker slot for Arpit\n\n### EUROPE\n\n- March 23, 2024 - March 24, 2024 | [Money Motion 2024](https://moneymotion.com/) | Zagreb, Croatia | Money Motion\n- March 27, 2024 - March 30, 2024 | [ETH Bucharest | Bucharest, Romania](https://www.ethbucharest.xyz/) | ETH Bucharest 👉 DevHub will be present at the event \n- March 18, 2024 - March 20, 2024 | [Digital Asset Summit](https://www.blockworks.co/) | London | Blockworks\n- April 8-12, 2024 | [Paris Blockchain Week](https://www.parisblockchainweek.com/) | Paris, France | | NF leading; Chris D speaking\nApril 12-14, 2024 | [ETHDam](https://www.ethdam.com/) | Amsterdam, Netherlands | ETHDam | DevHub\n\n### SOUTH AMERICA\n\n- March 22nd - March 24 | [ETHSamba](https://ethsamba.org/) | Brazil 👉 DevHub DevRels / NEAR Campus will be present at the event\n\n### THE UNITED STATES \n\n- March 20, 2024 - March 22, 2024 | IWB 2024 | DC area\n- April 3-5, 2024 | [NFT.NYC](https://www.nft.nyc/) | New York, NY | NFT.NYC\n- April | San Francisco | Funding the Commons (AI Focused Day) | FtheC | Banyan + EDGE\n- April 18-19, 2024 | The Institutional Crypto Conference East | New York, NY \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\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### Quote of the week: \n\n**Efte** from tools community: \"I Just wanna give a big shoutout to Lyudmil (DevHub DevRel) who has just spent multiple hours explaining the ins and outs of a fungible token contract with me. I am sure I will now not only be able to interact and create those, but also have a better overview of what sources to go to whenever I am stuck with other examples. I will put this to the test soon by creating contracts interacting with the ft contracts on different levels.\"\n\n  \n###### NEAR Dev NEWS is curated by the NEAR Dev NEWS group , and maintained by @victorkanu1.near & @orangejoe.near \n\n  \n![Sample Image](https://i.ibb.co/MDJ5zZn/2024-04-03-16-10-19.jpg)\n\n\n\n\n\n\n\n##### Thanks for reading, See you Next Week!", "metadata": { "title": " NEAR Dev NEWS #7", "createdAt": "2024-04-11", "updatedAt": "2024-04-11", "publishedAt": "2024-04-11", "status": "DRAFT", "subtitle": "Engage with NEAR", "description": "Engage with NEAR", "author": "victorkanu1.near", "id": "3235", "category": "news", "communityAddonId": "blogv2" } } } } }
SuccessReceiptId:
2taVChbrg1qdiVV7yHAqVh4Sr89QdjJMjGQAu4BF6iGo
No logs
Receipt:
Predecessor ID:
Receiver ID:
Gas Burned:
13 Tgas
Tokens Burned:
0.00133 
Called method: 'set' in contract: social.near
Arguments:
{ "data": { "neardevnews.community.devhub.near": { "blog": { "-near-dev-news-7-3235": { "": "\nWelcome to NEAR Dev NEWS, your prime source for the latest in the NEAR Developer ecosystem! NEAR lays the groundwork for all blockchain apps, offering an open-source system empowering devs to create fully decentralized, interoperable apps. Our Digest showcases developer progress and technical updates shaping the blockchain OS.\n\nIn this edition, we'll be exploring a plethora of updates and activities set out for the week, designed to keep you engaged with developers within the NEAR community. \n\n  \n### FEATURED RELEASES & PR's 🤩\n\n- **NEAR Rust SDK 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- `nearcore` **Version 1.39.0 has been released** this week and function call base cost is reduced. For small transactions like on [Cosmose](https://twitter.com/Cosmose_) and [hotdao](https://twitter.com/hotdao_), it is a 2x reduction in cost and 2x in throughput. RPC is now faster! Learn more 👉 [here](https://github.com/near/nearcore/releases)\n\n- `near-api-js` **Version 4.0.0 has been released**. It contains:\n\n👉 More than 36% bundle size reduction (from 380kb to 240kb). Info 👉[here](https://bundlephobia.com/package/near-api-js@4.0.0)\n👉 Failover RPC configuration\n👉 Executing view functions without the need of a Connection object and more!\n👉 You can read more about the changes 👉 [here](https://github.com/near/near-api-js/pull/1318)!\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  \n### DEVELOPER UPDATES 🛠\n\n- Users discussed tutorials for creating a bot to monitor transactions on the NEAR blockchain. Check out [NEAR Lake Framework Documentation](https://docs.near.org/concepts/advanced/near-lake-framework). It leverages pikespeak.ai 👉 [here](https://t.me/nearwatchbot). You can also check out [this repository](https://github.com/k-o-l-e-s/LNC-NEAR-watcher), a simple bot to get notified about TX's on NEAR's Mainnet.\n\n- Developers engaged in discussions about the possibility of NEAR's capability to sign Secp256k signatures for NFC chips. \n\n- Fast NEAR announces the new NEAR Data server! It's a simple and free alternative to the NEAR Lake Framework for data indexing. Click 👉 [here](https://twitter.com/fast_near/status/1777814928646197417) to learn more.\n\n- Developers discussed the validity period of signed transactions and the possibility of migrating contract state. They explored the technical aspects of transaction validity and contract state migration within the NEAR blockchain ecosystem.\n\n- Catch up on the recording of our live event with Hacken discussing WASM code coverage 👉 [here](https://twitter.com/i/spaces/1MYxNoAjnAXKw/peek?s=20).\n\n- NEAR Foundation Launches Infrastructure Committee with $4 Million in Funding. Learn more 👉 [here](https://pages.near.org/blog/near-launches-infrastructure-committee/)\n\n- A developer encountered a technical issue while attempting to broadcast a transaction on Ref with MNW, resulting in an error message. Discussions focused on diagnosing the cause of the issue, including potential reasons such as network connectivity problems or RPC issues.\n\n- Looking for a production ready rust contract made on `near-sdk` 5.1.0? Reference DevHub’s contract 👉 [here](https://github.com/NEAR-DevHub/neardevhub-contract).\n\n- Mark your calendar, starting this Thursday, DevHub will be streaming LIVE & unedited! Each week we will have guests to talk development, teach technical concepts, dev news, code reviews, and more. [Live on X](https://twitter.com/NEARDevHub) and [Twitch](https://twitch.tv/neardevhub). \n\n- Pagoda releases Chain Signatures that simplify user experiences by enabling users multichain access without leaving their NEAR account, unlocking billions of dollars in previously inaccessible liquidity.\n\n- Community members inquire about retrieving the epoch start block height via RPC. Ecosystem Devs suggests accessing it through the validators RPC endpoint, which you can find 👉 [here](https://docs.near.org/api/rpc/network#validation-status).\n\n- Seeking documentation about MultiSig on NEAR. Check out the MultiSig contract repository 👉 [here](https://github.com/near/core-contracts/tree/master/multisig).\n\n- Proximity labs shares Ideas for building with chain signatures 👉 [here](https://twitter.com/proximityfi/status/1774723437032038408?t=Y_oem9i384uPvwRIZKOuiw&s=35).\n\n- Developers requested a demo/tutorial for testing substream setup for NEAR blockchain.\n\n- User inquired about the availability of a no-std NEAR SDK. A link to nesdie repository was shared. 👉 [nesdie GitHub repository](https://github.com/austinabell/nesdie/).\n\n- Users discussed the challenges of retrieving token metadata, particularly for FTs, through various APIs. Suggestions for potential APIs were mentioned, such as [Fast NEAR](https://twitter.com/fast_near/status/1773398764859847008?t=9a8M8CwJqNBxNcW1p2d8DA&s=19) and [Pikespeak](https://doc.pikespeak.ai/).\n\n- Tools Community call and DevHub Livestream recordings are now available on [DevHub's Youtube](https://www.youtube.com/@NEARDevHub)\n\n- Developers provided an update on the signMessage issue and shared the latest developments on [GitHub](https://github.com/near/near-wallet/issues/3135).\n\n- Login functionality is being migrated to the wallet selector.\n\n- Developers discussed the challenges with wallet integration and offline signing standards. They referenced an [issue on GitHub](https://github.com/near/wallet-selector/issues/405) related to this topic.\n\n- The Protocol Work Group prepares to vote on NEP-536, a proposal to optimize NEAR protocol's performance. NEP-536 focuses on reducing the number of refund receipts, a significant contributor to runtime overhead. Don't miss this opportunity to contribute to the discussion 👉 [here](https://github.com/near/NEPs/pull/536).\n\n- Developers offered assistance on deleting a wallet and provided instructions on using a specific tool for the process. [Tool Link](https://lantstool.io/).\n\n- Developers Discussed changes in the Gas struct and its usage, particularly emphasizing the transition from manipulating raw integers to using dedicated constructors like `Gas::from_tgas()`. [Gas Struct Documentation](https://docs.rs/near-sdk/latest/near_sdk/struct.Gas.html).\n\n- Discussions continued on the handling of promises in code implementations, specifically regarding their execution and impact on transaction returns. Various considerations were raised regarding serialization and atomicity in NEAR Protocol transactions.\n\n- [NEAR protocol 2024 roadmap update](https://near.org/blog/near-q4-protocol-roadmap-update).\n\n- Jutsu.ai expressing interest in collaborating to onboard web2 developers to web3.\n\n\n  \n### THIS WEEKS TIPS 💡\n\n- `Tip`: A request was made to report broken links. The suggestion was to open an issue on the docs GitHub or make a PR with the proper link. The relevant link for documentation issues is 👉 [here](https://docs.github.com/).\n\n- `Tip`: Need to top-up USDT to a NEAR wallet on the test network? Use a faucet. [Faucet Link](https://near-faucet.io/).\n\n- `Tip`: Need help checking whether a NEAR account ID exists or not? Use the fetch API available via BOS to make an RPC query call to get account information.\n\n- `Tip` List of all the current NEAR Stakers: https://near-staking.com\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### 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 | **8th March 2024**\n- [NEP-491: Non-Refunable Storage](https://github.com/near/NEPs/pull/491) - Protocol Update | **26th Feb 2024**\n  \n\n**REVIEW STAGE**:\n\nSubject matter experts are currently reviewing the following NEPs. Some of the working group members are also deciding whether to accept or reject them. Feel free to explore, these NEPs will aid you during your development as you integrate them with your dApps. Share your thoughts and leave a comment.\n\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\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### ETHDam 🏆\n\nAt the ETHDam Hackathon, you can engage with NEAR's ecosystem through various avenues. Joining the event's chat allows for networking ([ETHDam Hackathon chat](https://t.me/+l1hv9RxZCCVkNzA0)), while Owen offers on-site support. NEAR's bounty program provides lucrative opportunities, including the [Chain Signatures](https://linktr.ee/chainsignatures) bounty offering $3,000 in USDC for innovative use cases of the Chain Signatures API, and the \"Power your startup with NEAR\" bounty, also with a $3,000 prize, for integrating startups with NEAR's technology stack. \n\nCriteria for submissions and judging prioritize creativity, quality, and technical excellence, with resources like [NEAR Components](https://docs.near.org/build/near-components/what-is) and [NEAR testnet faucets](https://near-faucet.io/) available for support. By engaging with NEAR, developers can explore cutting-edge technologies and compete for substantial prizes at the hackathon.\n\n\n  \n### HACKS OF THE WEEK 👨‍💻🏆\n\n- Check out the RPC Selector browser extension for NEAR, allowing you to customize RPC endpoints for dapps and wallets: [GitHub - RPC Selector](https://github.com/Sliman4/rpc-selector)\n\n**Building something on NEAR?** Share your project with the community! Tell us about it in the documentation community group, and get featured. Click 👉 [here](https://t.me/neardocscg).\n\n\n\n  \n### STAKEWARS 🚀\n**Participating in Stakewars? Here are some quick news and notes you should be aware of.**\n\n- The community announced the temporary suspension of operations on StatelessNet due to challenges in meeting required standards. This decision aims to ensure a more stable experience for all participants.\n\n- The Stake Wars IV program concluded, with plans to potentially restart the program in the future. Participants were thanked for their participation in the event.\n\n- As long as you are qualified for the reward program details we shared and followed the step to onboard with StatelessNet, you should get a reward.\n\n- The team plans to finalize reward distribution and send rewards by the end of this week. Rewards for validators will be sent to the owner ID of the staking pool contract on mainnet, as provided during registration.\n\n- When we resume StatelessNet, the network may start from a fresh state, requiring major updates. Keeping nodes up during this period may not be beneficial.\n\n- We'll inform the community once we start accepting proposals for the traffic generation program again.\n\n- There's a possibility of restarting the program later. We'll keep you updated on any developments. Thank you all for participating in Stake Wars IV!\n\n\n\n\n  \n### CHAIN ABSTRACTION COMMUNITY 🤩\n\nThe chain abstraction community has been actively engaged in discussions and developments aimed at enhancing interoperability and standardization across different blockchain networks.They have been exploring techniques like Multi-Party Computation (MPC) to address security and key management concerns. Discussions around key rotation within MPC systems have been gaining traction, as highlighted in recent community exchanges. As part of ongoing efforts to streamline development practices, there have been discussions on standardized deployment data storage practices, with community members advocating for transparent and accessible repositories of contract deployment information. \n\nCheck out this 👉 [GitHub repository](https://github.com/near/mpc-recovery) containing code for MPC contracts, illustrating the implementation of payload-based key management for chain signature requests and responses.\n\nFor further details, you can refer to the following links:\n\n👉 [Chain Signatures Documentation](https://docs.near.org/concepts/abstraction/chain-signatures)\n👉 [NEAR Multichain Example](https://github.com/near-examples/near-multichain)\n👉 [Chain Signatures Use Cases](https://docs.near.org/concepts/abstraction/signatures/use-cases)\n👉 [FastAuth SDK Documentation](https://docs.near.org/tools/fastauth-sdk)\n👉 [NEAR NFT Minting on Farcaster](https://warpcast.com/brower1/0xab61fd1b)\n\n[Learn more about the Chain Abstraction Community](https://near.social/devhub.near/widget/app?page=community&handle=chain-abstraction)\n\n\n  \n### CALL FOR CONTRIBUTORS 📞\n\n- Ecosystem developers propose a devcontainer image for examples encompassing both Rust and Node tooling. Volunteers are welcomed to contribute to `near-devcontainers` and test the additional container on examples. [Join Tools Community](https://t.me/NEAR_Tools_Community_Group)\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- 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- With the upcoming SDK 5.1 release, there will be updates needed in transitioning from #[near_bindgen] to #[near]. Matias is working on documentation updates, but additional assistance may be required. Don't hesitate to reach out if you can lend a hand! Reach out to [Docs community](https://t.me/neardocscg).\n\n- Given the release of the new SDK, both docs and example repositories need updating. If you want to contribute , [join the Docs Community Group](https://near.social/devgovgigs.near/widget/gigs-board.pages.community.activity?handle=documentation).\n\n- Check out [DevHub's On-Chain Quests](https://near.social/devhub.near/widget/app?page=community&handle=challenges) ⛳️, where you'll find a dynamic array of challenges across various communities, earning recognition and respect as you conquer each one! \n\n\n  \n# UPCOMING EVENTS \n\n\n### ONLINE:\n- April 18, 2024 | Contract Standards WG Call #5 | [Add to your calendar](https://bit.ly/3UcYyfW)\n- April 17 | Documentation community call | [Add to your Calendar](https://calendar.google.com/calendar/u/0/r/eventedit/copy/NjhpcWZjN20yaGxvdnMzdjg2Mm45MGdtYWRfMjAyNDA0MTdUMTcwMDAwWiBjX2Y1NGVkMzdmZDkyMzI3YWNkYzdlNDM0M2ZlNDA3MjJhZTU3OTdiNmM4MjkyOWJhOTNlOWYzYTg5YzY5NjU3YWJAZw)\n- Chain Abstraction Community Call | Coming soon \n- Thursdays 5PM UTC | **DevHub Livestreams** | [Live on X](https://twitter.com/NEARDevHub) and [Twitch](https://twitch.tv/neardevhub)\n\n### ASIA:\n\n- March 26, 2024 - March 27, 2024 | WOW Summit | Hong Kong \n- March 27, 2024 - March 28, 2024 | [BUIDL Asia | Seoul, Korea](https://www.buidl.asia/) | KryptoSeoul 👉 NEAR Foundation and Korea Hub will be present at the event \n- March 29, 2024 - March 31, 2024 | [ETH Seoul | Seoul, Korea](http://www.ethseoul.org/) | KryptoSeoul, Dystopia Labs 👉 DevHub and NEARWEEK will be present at the event \n- April 6-9, 2024 | Hong Kong Web3 Festival 2024 | Hong Kong | HashKey and Wanxiang | BD to speak\n\n### MIDDLE EAST\n- April 15-16, 2024 | [Blockchain Life 2024](https://blockchain-life.com/asia/en/spring2024/?utm_source=google&utm_medium=organic) | Dubai | Blockchain Life | NEAR Foundation, Arpit has a speaker slot\n- April 18-19, 2024 | [Token 2049 Dubai](https://www.dubai.token2049.com/) | Dubai | | NEAR Foundation organizing booth. Illia, Chris speaking\n- April 22-23, 2024 | World Blockchain Summit 2024 | Dubai | Trescon | NEAR Foundation, tentative speaker slot for Arpit\n\n### EUROPE\n\n- March 23, 2024 - March 24, 2024 | [Money Motion 2024](https://moneymotion.com/) | Zagreb, Croatia | Money Motion\n- March 27, 2024 - March 30, 2024 | [ETH Bucharest | Bucharest, Romania](https://www.ethbucharest.xyz/) | ETH Bucharest 👉 DevHub will be present at the event \n- March 18, 2024 - March 20, 2024 | [Digital Asset Summit](https://www.blockworks.co/) | London | Blockworks\n- April 8-12, 2024 | [Paris Blockchain Week](https://www.parisblockchainweek.com/) | Paris, France | | NF leading; Chris D speaking\nApril 12-14, 2024 | [ETHDam](https://www.ethdam.com/) | Amsterdam, Netherlands | ETHDam | DevHub\n\n### SOUTH AMERICA\n\n- March 22nd - March 24 | [ETHSamba](https://ethsamba.org/) | Brazil 👉 DevHub DevRels / NEAR Campus will be present at the event\n\n### THE UNITED STATES \n\n- March 20, 2024 - March 22, 2024 | IWB 2024 | DC area\n- April 3-5, 2024 | [NFT.NYC](https://www.nft.nyc/) | New York, NY | NFT.NYC\n- April | San Francisco | Funding the Commons (AI Focused Day) | FtheC | Banyan + EDGE\n- April 18-19, 2024 | The Institutional Crypto Conference East | New York, NY \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\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### Quote of the week: \n\n**Efte** from tools community: \"I Just wanna give a big shoutout to Lyudmil (DevHub DevRel) who has just spent multiple hours explaining the ins and outs of a fungible token contract with me. I am sure I will now not only be able to interact and create those, but also have a better overview of what sources to go to whenever I am stuck with other examples. I will put this to the test soon by creating contracts interacting with the ft contracts on different levels.\"\n\n  \n###### NEAR Dev NEWS is curated by the NEAR Dev NEWS group , and maintained by @victorkanu1.near & @orangejoe.near \n\n  \n![Sample Image](https://i.ibb.co/MDJ5zZn/2024-04-03-16-10-19.jpg)\n\n\n\n\n\n\n\n##### Thanks for reading, See you Next Week!", "metadata": { "title": " NEAR Dev NEWS #7", "createdAt": "2024-04-11", "updatedAt": "2024-04-11", "publishedAt": "2024-04-11", "status": "DRAFT", "subtitle": "Engage with NEAR", "description": "Engage with NEAR", "author": "victorkanu1.near", "id": "3235", "category": "news", "communityAddonId": "blogv2" } } } } } }
Result:
{ "block_height": "120516298" }
No logs
Receipt:
Predecessor ID:
Gas Burned:
223 Ggas
Tokens Burned:
0 
Transferred 0.01637  to petersalomonsen.near
Empty result
No logs
Receipt:
Predecessor ID:
Gas Burned:
223 Ggas
Tokens Burned:
0 
Transferred 0.0005  to petersalomonsen.near
Empty result
No logs