Application HIPs may be used to standardize software in the Hedera ecosystem that aren't mirror or consensus nodes. This includes application network software, external contract validators, multi-sig oracles, persistence mechanisms, enterprise software plugins, etc. An example of an Application HIP would be the Stablecoin Contract standard proposal and Non-fungible Token Contract written in Java as a layer-2 solution using the Hedera Consensus service to maintain trust.


NumberTitleAuthorNeeds Council Approval Release
820 Integration of Wallet Connect 2.0 Protocol for Wallets and dApps on Hedera Jason Fabritz No
775 Filter API in JSON-RPC Relay Georgi Lazarov No
745 Optionally send transaction data without required transaction fields Greg Scullard No
694 Real-time events in JSON-RPC Relay Ivo Yankov No
482 JSON-RPC Relay Mitchell Martin, Steven Sheehy No
478 Interoperability Between Smart Contracts and HCS John Conway, Walter Hernandez, Mohsin Qamar, Michael Garber, Pathorn Tengkiattrakul No
338 Signature and Wallet Providers Daniel Akhterov No
323 C SDK Greg Scullard, Romain Menetrier No
254 Swift SDK Soochul Yang No
179 External Transaction Signing for SDK and other clients Danno Ferrin No
30 CAIP Identifiers for the Hedera Network Danno Ferrin No
27 DID improvements to offer a broader support and interoperability for the Hedera DID method Jo Vercammen No
13 Hedera Name Service H. Bart No
11 Layer-2 Smart Contract Network Bryce Doganer, Lucas Henning No


NumberTitleAuthorNeeds Council Approval Release
29 JavaScript DID SDK Daniel Norkin No
28 Guardian Type Solution Matthew Smithies, Wes Geisenberger, Serg Metelin, Ken Anderson, Daniel Norkin, Prernaa Agarwal No
19 Decentralized Identifiers in Memo Fields Nick White, Jonathan Padilla, Atticus Francken, Steve Frenkel, Alex McComb, Daniel Norkin No
15 Address Checksum Leemon Baird Yes


NumberTitleAuthorNeeds Council Approval Release
762 AnonCreds Verifiable Data Registry Sumabala Nair No


NumberTitleAuthorNeeds Council Approval Release
22 ZKP-based Selective Attribute Disclosure in the DID SDK Maurizio Binello, Tim McHale No