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
22 ZKP-based Selective Attribute Disclosure in the DID SDK Maurizio Binello, Tim McHale No


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


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