# \#polkadot-sdk

**URL:** https://forum.polkadot.network/tag/polkadot-sdk/75.md

[Latest](https://forum.polkadot.network/latest.md) · [Categories](https://forum.polkadot.network/categories.md) · [Tags](https://forum.polkadot.network/tags.md)

---

## [Exploring the potential for a shared geospatial service as a common primitive for Polkadot Products and JAM.](https://forum.polkadot.network/t/exploring-the-potential-for-a-shared-geospatial-service-as-a-common-primitive-for-polkadot-products-and-jam/18746)

<div class="topic-metadata">

**Author:** [@C.M](https://forum.polkadot.network/u/C.M)\
**Replies:** 0\
**Last updated:** [September 24, 2026, 9:13am UTC](https://forum.polkadot.network/t/exploring-the-potential-for-a-shared-geospatial-service-as-a-common-primitive-for-polkadot-products-and-jam/18746 "2026-09-24T09:13:00Z")

</div>

Could Polkadot use a native Geospatial Service as a common primitive for Products and JAM? I have been thinking about a potentially missing primitive in the Polkadot Products/JAM stack: geospatial infrastructure. I don’…

---

## [Clarifying the Polkadot SDK database roadmap: RocksDB, ParityDB, and NOMT](https://forum.polkadot.network/t/clarifying-the-polkadot-sdk-database-roadmap-rocksdb-paritydb-and-nomt/17877)

<div class="topic-metadata">

**Author:** [@ross](https://forum.polkadot.network/u/ross)\
**Replies:** 1\
**Last updated:** [June 14, 2026, 12:21pm UTC](https://forum.polkadot.network/t/clarifying-the-polkadot-sdk-database-roadmap-rocksdb-paritydb-and-nomt/17877 "2026-06-14T12:21:45Z")

</div>

As of 13 June 2026, the Polkadot SDK database story looks unclear from the outside. RocksDB remains the effective default in normal SDK builds, ParityDB is supported but not default, and NOMT/binary-trie support exists a…

---

## [Proposal: Enable GitHub Discussions in paritytech/polkadot-sdk](https://forum.polkadot.network/t/proposal-enable-github-discussions-in-paritytech-polkadot-sdk/17824)

<div class="topic-metadata">

**Author:** [@ross](https://forum.polkadot.network/u/ross)\
**Replies:** 3\
**Last updated:** [June 12, 2026, 11:17am UTC](https://forum.polkadot.network/t/proposal-enable-github-discussions-in-paritytech-polkadot-sdk/17824 "2026-06-12T11:17:12Z")

</div>

I would like to propose enabling GitHub Discussions on the paritytech/polkadot-sdk repository. At the moment, the issue tracker contains a mixture of genuine code issues, bugs, implementation tasks, feature requests, de…

---

## [A deep dive into overhauling litep2p's ping protocol to support periodic pinging, spec-compliant payloads, and a new SubstreamKeepAlive mechanism for connection lifecycle management](https://forum.polkadot.network/t/a-deep-dive-into-overhauling-litep2ps-ping-protocol-to-support-periodic-pinging-spec-compliant-payloads-and-a-new-substreamkeepalive-mechanism-for-connection-lifecycle-management/17501)

<div class="topic-metadata">

**Author:** [@dharjeezy](https://forum.polkadot.network/u/dharjeezy)\
**Replies:** 0\
**Last updated:** [April 12, 2026, 5:51am UTC](https://forum.polkadot.network/t/a-deep-dive-into-overhauling-litep2ps-ping-protocol-to-support-periodic-pinging-spec-compliant-payloads-and-a-new-substreamkeepalive-mechanism-for-connection-lifecycle-management/17501 "2026-04-12T05:51:59Z")

</div>

Fixing litep2p’s Broken Ping Protocol (And the Connection Keep-Alive Redesign It Required) litep2p is the networking library behind Polkadot SDK. It’s a Rust implementation of libp2p, the protocol suite that handles eve…

---

## [\[Revive\] Deterministic Verifiable Contracts](https://forum.polkadot.network/t/revive-deterministic-verifiable-contracts/16042)

<div class="topic-metadata">

**Author:** [@Lohann](https://forum.polkadot.network/u/Lohann)\
**Replies:** 10\
**Last updated:** [November 27, 2025, 8:49pm UTC](https://forum.polkadot.network/t/revive-deterministic-verifiable-contracts/16042 "2025-11-27T20:49:49Z")

</div>

Motivation When implementing a smart-contracts that handles a lot economic value you really want to make sure it isn’t vulnerable, a smart-contract is immutable and once a vulnerability is exploited there’s no rollback, …

---

## [RFC-0152: Decentralized Convex-Preference Coretime Market for Polkadot](https://forum.polkadot.network/t/rfc-0152-decentralized-convex-preference-coretime-market-for-polkadot/13656)

<div class="topic-metadata">

**Author:** [@labormedia](https://forum.polkadot.network/u/labormedia)\
**Replies:** 0\
**Last updated:** [July 7, 2025, 5:38pm UTC](https://forum.polkadot.network/t/rfc-0152-decentralized-convex-preference-coretime-market-for-polkadot/13656 "2025-07-07T17:38:17Z")

</div>

The up-to-date Pull Request is available at RFC-0152 RFC-0152: Decentralized Convex-Preference Coretime Market for Polkadot Start Date 2025-06-30 Description This RFC proposes a decentralized market mechanis…

---

## [Runtime Misconfigurations in Polkadot: Risks and Mitigations](https://forum.polkadot.network/t/runtime-misconfigurations-in-polkadot-risks-and-mitigations/12527)

<div class="topic-metadata">

**Author:** [@srlabs](https://forum.polkadot.network/u/srlabs)\
**Replies:** 0\
**Last updated:** [April 15, 2025, 8:42am UTC](https://forum.polkadot.network/t/runtime-misconfigurations-in-polkadot-risks-and-mitigations/12527 "2025-04-15T08:42:43Z")

</div>

This post is the result of collaborative work between the Parity Security team and Security Research Labs. In our previous post “Security insights and trends from Alpha 2022-2024”, we talked about the Alpha program, whi…

---

## [Polkadot SDK 2024 Recap](https://forum.polkadot.network/t/polkadot-sdk-2024-recap/11528)

<div class="topic-metadata">

**Author:** [@kianenigma](https://forum.polkadot.network/u/kianenigma)\
**Replies:** 0\
**Last updated:** [January 24, 2025, 11:34am UTC](https://forum.polkadot.network/t/polkadot-sdk-2024-recap/11528 "2025-01-24T11:34:32Z")

</div>

While a bit late to publish it as a roundup at the end of 2024, I have written a summary of some of the new features that have landed in Polkadot SDK in 2024. This includes some of the topics already discussed here: Mo…
