Story Engineers

797 posts

Story Engineers banner
Story Engineers

Story Engineers

@StoryEngs

Building the world's IP blockchain.

Palo Alto, CA Katılım Ağustos 2024
7 Takip Edilen51.8K Takipçiler
Story Engineers
Story Engineers@StoryEngs·
What’s changed • fix: merged upstream security patch in #151 • p2p: added DNS resolution support for bootnodes in #152
English
2
1
13
353
Story Engineers
Story Engineers@StoryEngs·
Yasunari (Story-Geth v1.2.1) ⚠️ This release merges upstream security patches addressing CVE-2026-26314 and CVE-2026-26315, and added DNS resolution support for bootnodes. If you're running a node, upgrading is required. Read More ↴
English
5
3
23
1.1K
Story Engineers
Story Engineers@StoryEngs·
New getNFTBalance API on NftClient • Accepts spgNftContract (required) and owner (optional; defaults to connected wallet). • Returns bigint representing the NFT balance for the address.
English
1
0
5
237
Story Engineers
Story Engineers@StoryEngs·
Story Protocol TypeScript SDK v1.4.4 is live. This patch release includes: • Account Abstraction (AA) wallet support • Chain-based currency token validation • New getNFTBalance API on NftClient Details below ↴
English
6
5
42
1.6K
Story Engineers
Story Engineers@StoryEngs·
Story Protocol Python SDK v0.3.18 is now live. This release introduces powerful query helpers + batch operations to streamline IP workflows. Here’s what’s new ↴
English
14
12
93
6.3K
Story Engineers
Story Engineers@StoryEngs·
New to your vibe-coding journey? Tired of seeing "we're cooked" / "it's so over" all over the TL? → Join us for Local Host 3000 in 1 hour ← We got you covered on all the basics you need. Let's explore error-handling together ↓
English
11
3
41
17.1K
Story Engineers
Story Engineers@StoryEngs·
Later today on Local Host 3000, we'll go deeper on our recursively looped app and make design tweaks via Claude’s frontend agent skills. The further we go, the better we optimize. ▸ Today, Feb 18, 2pm ET ▸ Every Weds on @StoryEngs luma.com/l4wpou68
English
0
0
15
383
Story Engineers
Story Engineers@StoryEngs·
Common vibe-coding mistakes: • Confusing luck with workflows • Skipping planning (Plan≠Build) • Costly tabs by being sloppy Tips to level up: • Accounting for AEO in your GTM • Separating Plan mode from Build mode • Building for agents as users Alpha from @StoryEngs
English
12
14
74
3.4K