Filter
Exclude
Time range
-
Near
Replying to @delete19991224
呼び方:deletekey 好感度:大 家族にするなら:兄 リアルで会えるか:だめー 告白されたら:無理 ブロックされたら:病む 一言:もっと絡も!! このツイートやるか:やれたら!
1
17
WEEKLY UPDATE FROM THE REPOS OF NEAR [05-12.02.2026] The devs are cooking. Here's what shipped this week across the NEAR repositories! 📟 1/ STORE API SIMPLIFICATION - nearcore What changed: • Changed `Store::write()`, `Store::flush()`, and `Store::compact()` to return `()` instead of `io::Result<()>` • Removed redundant `.unwrap()` and `.expect()` calls from all usage sites • Updated test helpers and estimator context to handle infallible methods Why it matters: This pull request (github.com/near/nearcore/pul…) simplifies the store API by removing redundant error handling for methods that delegate to infallible database operations. 2/ OPENRPC GENERATOR - nearcore: JSON-RPC Specification Support What changed: • Adds OpenRPC 1.3.2 specification generator alongside existing OpenAPI • Implements schema transforms for cleaner code generation (FlattenOptionFix, MergePropertiesIntoOneOf, AddVariantTitles) • Upgrades schemars dependency from 1.0.3 to 1.2.1 • Generates openrpc.json file when running near-jsonrpc-openapi-spec Why it matters: This pull request (github.com/near/nearcore/pul…) enables accurate JSON-RPC client generation without manual hacks, improving developer experience for building type-safe clients in Rust and TypeScript. 3/ GAS KEY SAFETY - nearcore: Prevent accidental fund loss What changed: • Added 1 NEAR threshold for gas key deletion via `DeleteKey` action • Added 1 NEAR total balance check for account deletion via `DeleteAccount` action • Introduced `GasKeyBalanceTooHigh` error variant and `MAX_BALANCE_TO_BURN` constant • Refactored `remove_account` to eliminate redundant balance computations • Added comprehensive unit tests for boundary conditions Why it matters: This pull request (github.com/near/nearcore/pul…) implements NEP 611 (github.com/near/NEPs/pull/61…) protection against accidental large fund burns when deleting gas keys or accounts. 4/ NEW RELEASE - cloud-api v0.1.12 What changed: • Added rerank, score, and audio transcription endpoints for enhanced AI capabilities • Introduced /v1/usage API for external systems to record usage events • Added image generation, editing, and analysis support in Responses API • Implemented /v1/check_api_key endpoint for external model gateway authentication • Enhanced tool call support with function call orchestration and security hardening Why it matters: This release (github.com/nearai/cloud-api/…) significantly expands the API's AI capabilities with multiple new endpoints and improves external integration options for usage tracking and authentication. 5/ NEW RELEASE - near-jsonrpc-client-kotlin v1.0.20 What changed: • Added support for multiple RPC URLs with new `RpcUrls` configuration • Updated client initialization from `baseUrl` to `rpcUrls = RpcUrls.Single("rpc.mainnet.near.org")` • Regenerated client models from OpenAPI specification with updated serializers • Added new NEAR protocol models including `GasKeyInfo`, `TransferToGasKeyAction`, and `WithdrawFromGasKeyAction` Why it matters: This release (github.com/near/near-jsonrpc…) enables better RPC endpoint management and stays current with NEAR protocol updates - update your client initialization to use the new `rpcUrls` parameter. 6/ NEW RELEASE - near-jsonrpc-client-kotlin v1.0.22 What changed: • Fixed app compile error by changing `rpcUrls` parameter to `baseUrl` in client initialization • Regenerated client models and serializers from OpenAPI specification • Added new models for gas key operations: `GasKeyInfo`, `TransferToGasKeyAction`, `WithdrawFromGasKeyAction` • Removed deprecated `DynamicReshardingConfigView` model • Updated multiple serializers with new `BlindUnionSerializer` implementation Why it matters: This release (github.com/near/near-jsonrpc…) fixes breaking changes and keeps the Kotlin client synchronized with the latest NEAR RPC API updates - essential for developers using gas key features. 7/ NEW RELEASE - near-jsonrpc-client-kotlin v1.0.21 What changed: • Added support for multiple RPC URLs with simplified configuration using `listOf("rpc.mainnet.near.org")` • Regenerated client models and serializers from OpenAPI specification • Added new models for gas key operations: `GasKeyInfo`, `TransferToGasKeyAction`, `WithdrawFromGasKeyAction` • Removed deprecated `DynamicReshardingConfigView` model • Updated serializers with new `BlindUnionSerializer` implementation Why it matters: This release (github.com/near/near-jsonrpc…) adds failover support for RPC endpoints and keeps the client synchronized with the latest NEAR protocol changes - update for improved reliability and new feature compatibility. 8/ NEW RELEASE - near-jsonrpc-client-py v1.0.30 What changed: • Regenerated client models from OpenAPI specification with numerous updates • Added new models for gas key operations (GasKeyInfo, WithdrawFromGasKeyAction) • Updated CI/CD workflow configuration with significant changes • Fixed specific bugs in model generator and removed redundant strict_model file Why it matters: This release (github.com/near/near-jsonrpc…) ensures Python client stays in sync with NEAR RPC API changes and adds support for new gas key functionality. 9/ SANDBOX JOBS - ironclaw: Docker Container Execution System What changed: • Added orchestrator/worker architecture for running jobs in isolated Docker containers • Implemented per-job bearer tokens and secure container lifecycle management • Added Claude Code mode integration for running Claude CLI in containers • Created web gateway UI with real-time job monitoring and management • Added database persistence for sandbox jobs with project directory management Why it matters: This pull request (github.com/nearai/ironclaw/p…) enables secure execution of AI agent tasks in isolated containers with proper access controls - developers can now run untrusted code safely while maintaining visibility through the web interface. 10/ TELEGRAM CHANNEL IMPROVEMENTS - ironclaw What changed: • Added DM pairing infrastructure with PairingStore, CLI commands, and host APIs for secure user approval • Integrated Telegram channel with caption support for media messages and bot username stripping • Implemented /start command handling and configurable DM policies (open/allowlist/pairing) • Added comprehensive test coverage for pairing functionality and Telegram integration • Updated documentation with Telegram setup guide and building instructions Why it matters: This pull request (github.com/nearai/ironclaw/p…) enhances security with DM pairing for unknown users and improves Telegram integration with media caption support - developers should review the new TELEGRAM_SETUP.md for configuration details. 11/ NEW RELEASE - ironclaw v0.1.0 What changed: • Multi-provider LLM support via rig-core adapter • Sandbox jobs for secure command isolation • Google Suite & Telegram WASM tools integration • CLI improvements and interactive setup wizard • Fixed Linux keychain runtime panic Why it matters: This release (github.com/nearai/ironclaw/r…) establishes IronClaw's core functionality with multi-LLM support, security features, and tool integrations - essential for developers building privacy-focused AI agents. 12/ DOCS UPDATE - near-sdk-rs: Cross-Contract Call Documentation What changed: • Added comprehensive documentation for auto-generated `<ContractType>Ext` structs • Documented `ext()` and `ext_on()` constructors for cross-contract calls • Covered builder methods: `with_attached_deposit()`, `with_static_gas()`, `with_unused_gas_weight()` • Added cross-references from `#​[near(contract_state)]` and `#​[near]` macro sections • Explained how to discover method signatures via `cargo doc --lib` Why it matters: This pull request (github.com/near/near-sdk-rs/…) makes cross-contract call patterns discoverable and provides clear examples for NEAR smart contract developers. 13/ MACRO DOCS - near-sdk-rs What changed: • Added implementation details for #​[init], #​[payable], #​[private], #​[handle_result] attributes • Documented #​[near(event_json)] and #​[near(contract_metadata)] host function usage • Added documentation for previously undocumented #​[callback_result] and #​[callback_vec] attributes Why it matters: This pull request (github.com/near/near-sdk-rs/…) enables developers to understand macro-generated code without running cargo expand - useful for debugging and learning NEAR SDK internals. 14/ NEW RELEASE - private-chat v0.1.12 What changed: • Added conversation sharing functionality with public links and group management • Fixed response corruption when stopping during reasoning phase • Improved multi-model conversation display and response ordering • Implemented fallback models for chat title generation • Enhanced mobile UI styles and favicon visibility Why it matters: This release (github.com/nearai/private-ch…) enables collaborative AI conversations through sharing features while improving multi-model stability and mobile experience - key for teams using NEAR-based chat applications. 15/ SEARCH IMPROVEMENT - docs: Code Indexing Enhancement What changed: • Updated MeiliSearch indexing script to include code content in searchable documents • Modified package.json and SearchBar component to support enhanced search functionality Why it matters: This commit (github.com/near/docs/commit/…) improves documentation search by making code snippets discoverable - developers can now find relevant code examples more easily when searching the NEAR docs. 16/ FUNCTION CALL SUPPORT - cloud-api: Client-Executed Tool Integration What changed: • Added `FunctionCall` and `FunctionCallOutput` API models for client-executed tools • Implemented pause/resume flow with `incomplete` status and `function_call_required` reason • Added security validation for workspace ownership and call_id matching • Extended tool parsing to handle custom functions, code_interpreter, and computer tools • Added comprehensive E2E tests for single/parallel function calls Why it matters: This pull request (github.com/nearai/cloud-api/…) enables LLMs to request external function execution and resume conversations with results - developers can now integrate custom tools and external services into their AI workflows. Check out the full repositories: 1. github.com/near/nearcore 2. github.com/nearai/cloud-api 3. github.com/near/near-jsonrpc… 4. github.com/near/near-jsonrpc… 5. github.com/nearai/ironclaw 6. github.com/near/near-sdk-rs 7. github.com/nearai/private-ch… 8. github.com/near/docs Sign up and get the weekly NEAR ecosystem newsletter at: subscribe.nearweek.com
1
10
262
WHAT SHIPPED IN NEAR ECOSYSTEM [20.01] 📟 Gas keys implementation now supports NEP-611 with extended Add/DeleteKey actions and new QueryRequest::ViewGasKeyNonces, enabling developers to create and manage gas-specific keys through standard operations. github.com/near/nearcore/pul… nearcore: Block Header V6 adds shard split support for dynamic resharding during block sync ⚠️ breaking github.com/near/nearcore/pul… nearcore: Dynamic resharding configuration moved to EpochConfig for cleaner epoch management logic ⚠️ breaking github.com/near/nearcore/pul… chat-api: Chat API adds secure conversation sharing with cryptographically secure tokens and access controls ⚠️ breaking github.com/nearai/chat-api/p… Follow @nearprotocol devs → github.com/near | github.com/nearai
2
29
Here is a snipet of a heap datastructure here is a structure and declaration of all the core operations needed to maintain the min heap property The core operations: extractMin, deleteKey and a recursive method to heapify the subtree at given index
1
2
55
違うよ違う 謝罪なんてしなくていいのDeleteKey押す位の手間で消え去れって、ね?
4
49
置くべきか 置かざるべきかの 数千字 吐く息とめて いけDeleteKey
3
31
Replying to @strikitea
使ってるCADにもよるのですが、Fusionなら、面を選択してDeleteKeyでその面の削除を試みます。削除したあとは、周りの面の延長して補完しますよ。
1
4
163
20 Days 20 POC Breakdown Day 16 : CVE-2021-39226 In affected versions of Grafana, unauthenticated and authenticated users are able to view the snapshot with the lowest database key by accessing the literal paths: /dashboard/snapshot/:key, or /api/snapshots/:key. If the snapshot "public_mode" configuration setting is set to true (vs default of false), unauthenticated users are able to delete the snapshot with the lowest database key by accessing the literal path: /api/snapshots-delete/:deleteKey. Regardless of the snapshot "public_mode" setting, authenticated users are able to delete the snapshot with the lowest database key by accessing the literal paths: /api/snapshots/:key, or /api/snapshots-delete/:deleteKey. The combination of deletion and viewing enables a complete walk through all snapshot data while resulting in complete snapshot data loss. Exploit : github.com/grafana/grafana/s… POC's bugzilla.redhat.com/show_bug… cyrisk.com/security/mitigati… grafana.com/docs/grafana/lat… github.com/advisories/GHSA-6… my.f5.com/manage/s/article/K… suse.com/security/cve/CVE-20…

13
1,504
24 Dec 2023
Day 78 of learning #dsa #100DaysOfCode #javascript 🚀 #MinHeapify corrects the #heap property, deleteKey decreases key, extracts minimum, and extractMin #removes and returns the minimum element after replacing the root. #letsconnect #buildinpublic
9
2
33
1,505
Part 2: Near 2.2 ⭐⭐NEAR Account Model⭐⭐ Thực tế, từ những ngày đầu phát triển sản phẩm, NEAR Protocol đã tích hợp AA vào trong hạ tầng của mình. Đối với người dùng bình thường trên Etherum, chủ yếu họ thường sử dụng EOA Wallet cho một số tác vụ đơn giản, thì các ví trên NEAR thực hiện nhiều tác vụ phức tạp hơn như DeleteKey, Stake, Delegate, DeleteAccount, Transfer, AddKey, DeployContract, etc. ⭐Đơn giản định danh công khai Đối với Ethereum, các tài khoản sẽ được định danh thông qua 1 khóa công khai (Public Key), khóa công khai này là 1 chuỗi dài 64 kí tự được mã hóa từ khóa bí mật (Private Key) có dạng 0x123… . Người dùng cần dùng địa chỉ này để nhận chuyển khoản vào ví khi có nhu cầu. ⭐Quyền truy cập qua Access Keys Đây có thể nói là điểm nổi bật nhất của tài khoản trên NEAR so với Ethereum, cụ thể: Ethereum (hoặc một vài blockchain khác): 1 tài khoản thường sử dụng 1 khóa riêng tư (private key) để kí xác nhận giao dịch. NEAR Protocol: 1 tài khoản có thể sở hữu nhiều cặp khóa công khai/riêng tư khác nhau, mỗi khóa gọi là 1 khóa truy cập (Functioncall Key) được dùng cho một số quyền nhất định. Điều này sẽ giúp hạn chế khá nhiều rủi ro với các bên thứ ba khi họ có thể truy cập vào ví bạn. Ở trường hợp xấu có thể xảy ra, nếu bên thứ ba như smart contract của giao thức DeFi mới có lỗ hổng bảo mật bị khai thác: Ethereum: Khi họ truy cập vào private key của bạn sẽ gần như chiếm quyền kiểm soát hoàn toàn tài khoản. NEAR Protocol: Hacker chỉ có thể truy cập vào một vài tài sản bạn đã phân quyền trước cho tài khoản của bạn, vì thế họ không thể nào đánh cắp toàn bộ tài sản.
Part 1: AA là gì? Account Abstraction (AA) là một phương pháp để biến một tài khoản người dùng thành một hợp đồng thông minh. Giải pháp này giúp đơn giản hóa trải nghiệm người dùng (UX) và cho phép người dùng có thể giữ tài sản an toàn hơn. Starknet và zkSync, hai trong số các ZK-Rollups hàng đầu hiện nay, đã ra mắt với tính năng Account Abstraction (AA) tích hợp sẵn trên nền tảng của họ. Bên cạnh đó, Ethereum cũng đã có giải pháp cho ví AA thông qua EIP-4337. Các hoạt động gần đây liên quan đến AA trên hệ sinh thái Ethereum cho thấy ​​mức độ ứng dụng và tầm quan trọng của ví AA trong trải nghiệm người dùng thực tế. Bên cạnh Ethereum, NEAR Protocol cũng là một trong những L1 đầu tiên quan tâm đến AA trong thiết kế nền tảng và hạ tầng AA đã có sẵn trên NEAR từ khi mainnet 2020. Nguồn: GFI
18
16
953
〔進捗報告〕 最近発見したバグですが、何故かUnityのPlayerPrefsでは一部の機種だと、DeleteKeyを使ってもデータが削除できないっというバグがあったので セーブシステムを作り直しました、さらに暗号化もしました。 セーブ用スクリプトもツールで自動生成出来るので、個人としては結構使いやすい。
12
370
Delete a few uncertainties about your financial future by investing in SIPs. #MotilalOswal #MotilalOswalAMC #KeysofInvesting #ThinkEquityThinkMotilalOswal #keyboard #keys #deletekey
13
131
1,476
142,962
Time to hit the #DeleteKey on the keyboard and get rid of the negative people in my life. #FreeAtLast
3
5
89
27 Nov 2022
What I love about #TraditionalComicArt aside from the touch, feel, smell of the India ink on real paper (it’s non-toxic😁) #OriginalArt #1ofAKind is the #Imperfections #DigitalArt is PERFECT I know, I’ve explored it’s ease of use and when mistakes are made #DeleteKey and Voilà 🪄
3
今が潮時かな 笑顔が冷たく 口数も減り あれほど連絡し合っていたのは 遠い過去 君の吐息にが 溜息に聞こえ 終わりを迎えた 失恋の合図は 全てのdeletekey 終わりよければすべてよし 涙は家で 流そうか
失恋の合図 #引用リツイートで誰かが詩にしてくれる いつもありがとう(´꒳`*) ヨロ(`・ω・´)スク!
4
25
25 Jun 2022
Replying to @smk7758
試してないけどdeletekey取得apiとそれを使ってコメントを削除するっぽいapiを見つけたからやろうとすれば直叩きで行けると思いまふ...
1
1
3
なんでこんなこと思わなあんのやろ こんな辛いこと他にある? 人が人でなくなる 頭ん中のDeleteKey押せたらええのに 一瞬で記憶全部なくなればええのに そんなん出来たら苦しまんでええのに でも人の記憶はそうはいかん そんな簡単なことやない 機械とちゃう 生身の人間なんや
1
3
3 Jan 2022
Replying to @nav1n0x @sectest9
Congrats Try this too CVE-2021-39226 /api/snapshots/:key /api/snapshots-delete/:deleteKey /dashboard/snapshot/:key
1
3
15
Replying to @pdnuclei
grafana.com/blog/2021/10/05/… If the snapshot “public_mode” configuration setting is set to true (vs. default or false), unauthenticated users are able to delete the snapshot with the lowest database key by accessing the literal path: /api/snapshots-delete/:deleteKey
1
1