NEAR DevHub
1.23K subscribers
491 photos
30 videos
607 links
πŸ“’ Official announcements channel for NEAR DevHub. Join @neardev group for discussions. Learn more: at http://neardevhub.org.
Download Telegram
πŸ†• Introducing β€œAttention” β€” by Illia Polosukhin

Why we need user-owned, verifiably private AI β€” and how blockchains can help us get there πŸ’¬

In this new newsletter, Illia shares high-level insights at the intersection of AI and Web3:
πŸ”· Risks of corporate-owned AI & centralization
πŸ”· Why open, decentralized AI matters for our future
πŸ”· How crypto can provide identity, governance, and payments for AI
πŸ”· Building a state-of-the-art, user-owned AI ecosystem

We’re at a fork in the road: AI can either serve corporate profit & control β€” or empower users & communities. Read more in "Attention" πŸ‘‡

πŸ”– Subscribe & read

🟦 Channel | Chat | LinkTree
Please open Telegram to view this post
VIEW IN TELEGRAM
πŸ‘2❀1
🚨 New NDNA (#3) is live

1⃣ This week’s issue looks at how economic breakdowns can quietly kill blockchains β€” without a single hack or bug. Using Monero’s current β€œprofitability attack” as a case study, we explore how misaligned incentives push out good actors, centralize control, and drain life from a network.

2⃣ From privacy coins to DeFi airdrops, the pattern is the same: when the people who take the biggest risks aren’t rewarded, trust erodes. And when trust erodes, ecosystems can fade into β€œzombie chains” β€” alive in code, dead in practice.

⏳ NDNA blog now drops on Mondays β€” with the Podcast & YouTube versions released on Tuesdays.

NDNA is an opinionated weekly newsletter and podcast looking at the news in and around the NEAR developer ecosystem.

πŸ”ˆ Podcast | πŸ“Ί YouTube | πŸ“° Substack
Please open Telegram to view this post
VIEW IN TELEGRAM
πŸ‘4
New API Support for NEAR Builders πŸ‘¨β€πŸ’»

The NearBlocks API sponsorship is now open β€” with support from the NEAR Foundation & Infrastructure Committee 🫰

Plans & limits:
🟒 Startup ($79/mo): 400K calls/month · 150 calls/min
🟒 Standard ($299/mo): 3M calls/month · 400 calls/min
🟒 Professional ($899/mo): 9M calls/month · 900 calls/min

What you get:
🟒 Commercial use allowed
🟒 Comprehensive NEAR blockchain data via REST APIs
🟒 Same source that powers the NearBlocks Explorer
🟒 Professionally maintained, high-performance infra (GET via HTTP/cURL)

βž• More information about NearBlocks

πŸ”£ Deadline: ~45 days left
πŸ”£ Submit Now

🟦 Channel | Chat | LinkTree
Please open Telegram to view this post
VIEW IN TELEGRAM
πŸ”₯4❀1😁1
🚨 New NDNA (#4) is live

πŸ—― Bridge hacks have drained billions β€” but the real killer might be baked into how bridges work. This week, we look at how NEAR Intents flips the script, making cross-chain swaps seamless… and possibly ending the hacker’s favorite payday.

πŸ—― One shift could link every major chain β€” and change how we think about moving value forever.

After this, you might never look at β€œbridging” the same way again πŸ‘€

NDNA is an opinionated weekly newsletter and podcast looking at the news in and around the NEAR developer ecosystem.


πŸ”– Step onto the other side of the bridge and see what’s waiting:
πŸ”ˆ Podcast | πŸ“Ί YouTube | πŸ“° Substack
Please open Telegram to view this post
VIEW IN TELEGRAM
πŸ‘4
πŸ”₯2πŸ‘1
Rust Smart Contracts on NEAR β€” Lesson 5 πŸ¦€

Ownership & Borrowing

When you’re building NEAR smart contracts in Rust, ownership and borrowing are your guardrails for memory-safe, predictable code. In this lesson, you’ll learn how to use them to avoid bugs and keep your contracts clean and reliable πŸ’₯

✏️ What you’ll learn:
πŸ”΄ What is Ownership β€” how moves/copies prevent leaks & crashes
πŸ”΄ Borrowing β€” immutable & vs mutable &mut, and when to use each
πŸ”΄ Common mistakes & fixes β€” using moved values, multiple mutable borrows, forgetting to dereference in NEAR methods
πŸ”΄ Best practices for NEAR β€” &str vs String, when to clone() vs borrow, keeping borrow scopes short

πŸ“Ί Watch the lesson here
πŸ‘¨β€πŸ’» Code examples

πŸ”– Stay tuned β€” more lessons on efficient and secure NEAR smart contract development are on the way.

🟦 Channel | Chat | LinkTree
Please open Telegram to view this post
VIEW IN TELEGRAM
πŸ‘3
βœ‰οΈ NEAR Dev News #75 is out!

πŸ“Œ THIS WEEK’S FOCUS: Race of Sloths
Turn your GitHub PRs into on-chain reputation. A bot + NEAR-powered leaderboard that gamifies open-source contributions.

πŸ–₯ Also inside:
πŸ”΄ $300 + royalties bounty β€” design Black Dragon sports jerseys
πŸ”΄ DevHub winner: near-rpc-typescript (typed NEAR RPC for TypeScript)
πŸ”΄ NEARN hits $1M earned β€” 18 open bounties live
πŸ”΄ Chain Abstraction demo: one login, swaps across NEAR + Arbitrum
πŸ”΄ Shade Agents: Vlad Frolov on AI + privacy workflows
πŸ”΄ New Rust tutorials: initialization, ownership, borrowing
πŸ”΄ Mainnet upgrade 2.7.0 β†’ 9 shards live
πŸ”΄ Illia’s newsletter Attention β€” verifiable, user-owned AI

Someone farms XP in games, someone in races. The grind is the same β€” but the rewards are different 🌑

πŸ”— Read + subscribe: http://dev.near.org/newsletter
πŸ”– Available freelancing opportunities here

🟦 Channel | Chat | LinkTree
Please open Telegram to view this post
VIEW IN TELEGRAM
πŸ‘3❀1😍1
DevHub Bounty Winner: TypeScript RPC for NEAR

The β€œAutomate Generation of TypeScript RPC Client for NEAR Protocol” bounty goes to Peter Salomonsen πŸ†

near-rpc-typescript delivers a type-safe, auto-generated TypeScript client for NEAR JSON-RPC β€” generated from the official spec to speed up integrations.

Congrats and thanks for the great work, @petersalomonsen! πŸŽ‰

πŸ”— Bounty & Repository

🟦 Channel | Chat | LinkTree
Please open Telegram to view this post
VIEW IN TELEGRAM
πŸ”₯8❀7πŸ‘3πŸ₯°1
Near Studio β€” a VS Code extension for NEAR smart contracts

Build and deploy NEAR smart contracts right from your editor 😁

What it does:
βšͺ️ Compile & deploy contracts with quick commands
βšͺ️ Smooth developer workflow inside VS Code
βšͺ️ Makes experimenting on NEAR way faster

First release β€” try it today, ⭐️ the repo, and share your feedback/ideas or open a PR for @OxF3stus

🟦 Channel | Chat | LinkTree
Please open Telegram to view this post
VIEW IN TELEGRAM
πŸ”₯7
Also saves code review time, BUT if you don't agree...

πŸ‘‰ Just try it πŸ‘ˆ
Please open Telegram to view this post
VIEW IN TELEGRAM
πŸ‘6❀1
Good news for NEAR builders βœ”οΈ

... and data teams!
Apply to get $99/month Pikespeak API Package β€” for free!

🟒 Full access to the Pikespeak API
🟒 50+ NEAR portfolio & explorer endpoints
🟒 5 requests per second
🟒 150,000 requests/month included

Build smarter with the Pikespeak API 🫰

πŸ”£ Deadline: ~19 days left
πŸ”£ Submit Now

🟦 Channel | Chat | LinkTree
Please open Telegram to view this post
VIEW IN TELEGRAM
πŸ”₯2❀1
Rust Smart Contracts on NEAR β€” Lesson 6 πŸ¦€

Conditions (if, else, else if) and Compound Conditions (&&, ||)

When you’re building NEAR smart contracts in Rust, conditional logic is how your code makes smart choices. In this lesson, you’ll learn how to express rules, handle branches safely, and keep your dApps predictable and clear πŸ’₯

✏️ What you’ll learn:
πŸ”΄ What if / else are β€” making decisions from contract state & input
πŸ”΄ Comparison operators β€” ==, !=, <, <=, >, >= in practice
πŸ”΄ Else if chains β€” checking multiple cases in sequence
πŸ”΄ Compound conditions β€” combining rules with && (AND) and || (OR)
πŸ”΄ Live example β€” compile, deploy, and test outcomes based on conditions

πŸ“Ί Watch the lesson here
πŸ‘¨β€πŸ’» Code examples

πŸ”– Stay tuned β€” more lessons on efficient and secure NEAR smart contract development are on the way.

🟦 Channel | Chat | LinkTree
Please open Telegram to view this post
VIEW IN TELEGRAM
πŸ‘4❀1😘1
🚨 New NDNA (#5) is live

AI tools like Strawberry Computer promise to make coding as simple as describing your idea β€” β€œvibe coding” that can spin up apps in minutes. But if shipping becomes effortless, what happens to security, taste, and trust? πŸ€”

This week we look at the growing divide:
πŸ”· AI can generate code, but it can’t generate judgment
πŸ”· The flood of cookie-cutter, insecure apps β€” and what’s at stake when security fundamentals are skipped
πŸ”· Why the future belongs to builders who blend speed with product sense and rigorous testing

From insecure clones to the next wave of Web4 apps, the question isn’t whether AI can build β€” it’s whether the products are worth using πŸ—―

NDNA is an opinionated weekly newsletter and podcast looking at the news in and around the NEAR developer ecosystem.

πŸ”– Pick whichever format suits you best and get the details:
πŸ”ˆ Podcast | πŸ“Ί YouTube | πŸ“° Substack
Please open Telegram to view this post
VIEW IN TELEGRAM
πŸ‘4
Rust Smart Contracts on NEAR β€” Lesson 7 πŸ¦€

Loops
(for, while) & Safe Iteration

When you’re building NEAR smart contracts in Rust, loops power batch actions and list processing. In this lesson, you’ll learn to iterate efficiently, avoid unbounded work, and keep gas predictable πŸ’₯

✏️ What you’ll learn:
πŸ”΄ What loops are β€” repeating logic without duplicating code
πŸ”΄ For loops β€” ranges & iterators over collections you control
πŸ”΄ While loops β€” explicit exit conditions and state-driven flows
πŸ”΄ Step control β€” .step_by(), break, continue, enumerate()
πŸ”΄ Gas-safety patterns β€” caps, pagination/chunking, and early exits

πŸ“Ί Watch the lesson here
πŸ‘¨β€πŸ’» Code examples

πŸ”– Stay tuned β€” more lessons on efficient and secure NEAR smart contract development are on the way.

🟦 Channel | Chat | LinkTree
Please open Telegram to view this post
VIEW IN TELEGRAM
❀3πŸ‘1
Stop burning time β€” start shipping πŸ‘¨β€πŸ’»

Quick reminder: free RPC/API sponsorships are closing soon ⏳
Clock’s ticking β€” submit before the windows close:
πŸ”· Lava RPC β€” 5d left (Aug 31)
πŸ”· Pikespeak API β€” 16d left (Sep 11)
πŸ”· NearBlocks API β€” 34d left (Sep 29)
πŸ”· FastNear RPC β€” 35d left (Sep 30)

πŸ”– Don’t pay for infra you can get sponsored. Apply now

🟦 Channel | Chat | LinkTree
Please open Telegram to view this post
VIEW IN TELEGRAM
πŸ‘3❀1
Rust Smart Contracts on NEAR β€” Lesson 8 πŸ¦€

Match & Enums

Enums + match = expressive, total, bug-resistant logic. In this lesson, you’ll model contract state clearly, replace magic numbers/strings, and make branching explicit β€” all with compile-time guarantees πŸ’₯

✏️ What you’ll learn:
πŸ”΄ What enums are β€” and when to use them instead of ints/strings
πŸ”΄ match fundamentals β€” exhaustive branches, _ wildcard, guards
πŸ”΄ Domain modeling β€” UserTier::{Basic, Premium, VIP} and real logic
πŸ”΄ Storage & ABI tips β€” deriving traits, Borsh for state, Serde for views
πŸ”΄ Safety patterns β€” avoiding partial matches and hidden panics

πŸ“Ί Watch the lesson here
πŸ‘¨β€πŸ’» Code examples
What should we cover next? Drop it in the comments ✍️

πŸ”– Stay tuned β€” more lessons on efficient and secure NEAR smart contract development are on the way.

🟦 Channel | Chat | LinkTree
Please open Telegram to view this post
VIEW IN TELEGRAM
❀2
βœ‰οΈ NEAR Dev News #76 is out!

πŸ€‘ THIS WEEK’S FOCUS: PublicAI
People-powered data for AI β€” label β†’ validate β†’ consensus β†’ earn $PUBLIC. Portable on-chain reputation meets real rewards.

πŸ–₯ Also inside:
🟒 NEARN hits $1.24M earned β€” 15 open bounties live
🟒 $100 bounty β€” design Solvium mascot + sticker pack
🟒 Tooling update β€œNEAR Thanksgiving” β€” sandbox revamp + auto RPC clients
🟒 New tool: Sign in with NEAR (Better Auth plugin)
🟒 Global Contracts (mainnet) + near-sdk-rs 5.17.0
🟒 Virtual EVM Chains on NEAR with Aurora Cloud
🟒 Omni Bridge CLI β€” move ERC-20/SPL to NEAR as NEP-141
🟒 New Rust tutorials: conditions, loops, safe iteration

🫰 AI needs data. Now it pays.

πŸ”— Read + subscribe: http://dev.near.org/newsletter
πŸ”– Available freelancing opportunities here

🟦 Channel | Chat | LinkTree
Please open Telegram to view this post
VIEW IN TELEGRAM
πŸ‘4
Rust Smart Contracts on NEAR β€” Lesson 9 πŸ¦€

Arrays
What should we cover next? Drop it in the comments ✍️

Arrays look simple β€” fixed-size, same-type values β€” but in smart contracts they shine: predictable memory, fast lookups, and clear, bug-resistant logic. In this lesson we’ll use arrays to model real gameplay and governance data, and show when to reach for Vec or NEAR SDK collections instead πŸ’₯

✏️ What you’ll learn:
πŸ”΄ Array basics β€” declaring [T; N], indexing, iteration
πŸ”΄ Modern ops β€” iter().max(), contains(), swap(), sort()
πŸ”΄ Mutation patterns β€” updating scores, tallies, and snapshots safely
πŸ”΄ Safety tips β€” bounds checks with get(), avoiding panics, chunking work for gas
πŸ”΄ Choosing the right tool β€” arrays vs Vec vs NEAR SDK Vector for persistent state

πŸ“Ί Watch the lesson here
πŸ‘¨β€πŸ’» Code examples

πŸ”– Stay tuned β€” more lessons on efficient and secure NEAR smart contract development are on the way.

🟦 Channel | Chat | LinkTree
Please open Telegram to view this post
VIEW IN TELEGRAM
❀3
NEAR RPC docs got a refresh πŸ”„

The
Access Keys page is now easier to scan and copy into your code: a quick table of the four methods up top, clear params, and ready-to-use examples in JSON / JavaScript / HTTPie. There’s also a one-click β€œTry it out on Lantstool” to run calls immediately, plus a short Best Practices section πŸ—―

πŸ”— Page
πŸ”— Markdown

🟦 Channel | Chat | LinkTree
Please open Telegram to view this post
VIEW IN TELEGRAM
πŸ”₯9πŸ‘4
Rust Smart Contracts on NEAR β€” Lesson 10 πŸ¦€

HashMap
What should we cover next? Drop it in the comments ✍️

Need fast key β†’ value lookups? Use HashMap. In this lesson we model DeFi/NFT data, show safe updates, and when to switch to NEAR SDK’s persistent maps πŸ’₯

✏️ What you’ll learn:
πŸ”΄ Basics β€” HashMap<K, V>, new(), insert(), get(), contains_key()
πŸ”΄ Entry API β€” entry().or_insert() for clean increments/updates
πŸ”΄ Mutation + Option β€” remove(), retain(), unwrap_or, if let, ?
πŸ”΄ Safety β€” chunk work for gas, avoid unbounded loops; HashMap (in-call) vs UnorderedMap/LookupMap (persisted)

πŸ“Ί Watch the lesson here
πŸ‘¨β€πŸ’» Code examples

πŸ”– Stay tuned β€” more lessons on efficient and secure NEAR smart contract development are on the way.

🟦 Channel | Chat | LinkTree
Please open Telegram to view this post
VIEW IN TELEGRAM
πŸ‘3