Try   HackMD

Decentralized Inscription Service

[Need to check with Bob if it makes sense now]

Description

Ordinal inscriptions are metadata attached to a specific satoshi and are stored on the Bitcoin blockchain. The metadata is encoded in the witness data of a transaction. Usually, inscriptions are in the witness data of spending scripts of P2TR (Pay-to-Taproot) outputs. However, since the Internet Computer currently only supports threshold ECDSA signatures and not threshold Schnorr signatures, we can't inscribe using this approach. Lukily, there's also an approach using P2WSH spending scripts to encode inscriptions.

Requirements

Acceptance Critera

References

Open Internet Service for Ordinals data

Description

The current Bitcoin Canister on the Internet Computer only stores the set of unspent transaction outputs (UTXOs). This is not enough information to find out:

  • which ordinals are inside a given UTXO
  • to what level of rarety they belong
  • if they have an associated inscription

Until we have all this information on the Internet Computer, we want to encourage building a sustainable open internet service that allows fetching this information from third party indexing services using HTTPS outcalls.

Requirements

grant

Acceptance Critera

References

Multi-subnet custody (Multi-sig of tECDSA keys)

Description

The Internet Computer can be used to create Bitcoin wallets, where the private never exists physically, but signatures are generated by a secure multi-party computation among the nodes of a fiduciary subnet. However, for some very high value custody applications, we might want to increase the security even further.

Bitcoin Script allows to require multiple signatures to spend a UTXO. Hence, we can create a wallet (or even a version of ckBTC) that consists of multiple canisters running on different fiduciary subnets, requesting signatures derived from different master keys.

Hence, the node providers of multiple subnets would need to collude to steal assets.

Requirements

  • The wallet should be able to generate P2WSH addresses to send funds.

Acceptance Critera

References

Last changed by 
 
Dominic Wörner
0
89

Read more

ICP IBC integration

One of the core capabilities of ICP is threshold cryptography (Chain-Key Cryptography). Currently ICP subnets use Threshold BLS signatures to authenticate state and responses, and allow smart contracts to request ECDSA (over the Bitcoin curve secp256k10) signatures. Each smart contract has a dedicated path in the key derivation tree and can derive public keys and request signatures accordingly.

Jan 29, 2024
ICP Hackathon Cheat Sheet

Hey fellow hacker :wave: , great that you want to explore the capabilities and possibilities of the Internet Computer Protocol. We've compiled a list of resources to make starting off as simple as possible, and provide you a quick reference to find more information, tools and help. General Introduction Tweet thread sized pitch of ICP Introduction to ICP Introduction video from ETHDenver Comparison between different blockain platforms

Apr 25, 2023
BNT-X - Decentralized Exchange Data Interface

Overview Status: Draft Project Type: Cooperative - Multiple workers can submit work, and the bounty is shared Time Commitment: Weeks Experience Level: Intermediate Size: USD 25'000 in ICP (at time of distribution) Description In order to provide more visibility of the Internet Computer DeFi ecosystem, ICRC-1 tokens and decentralized exchanges should be listed on the popular financial data provider websites of the cryptocurrency industry, such as CoinMarketCap and DefiLlama. For this, the IC ecosystem needs to define and implement standard interfaces that meet the requirements of the financial data providers. The goal of this bounty is the creation of interface standards and implementations for AMM and orderbook-based decentralized exchanges (DEXes).

Apr 6, 2023
RFP-5 Canister-based Ethereum Light Client

Overview The work on the Bitcoin integration already does some heavy lifting for integrating other chains with the Internet Computer. Most notably, chain-key signing allows canisters on the Internet Computer to sign transactions targeting platforms that support ECDSA, and HTTPS outcalls allow to submit them without incentivizing 3rd party relayers. However, the approach to access Bitcoin state relies on a custom implementation in the Internet Computer replica software, and is as such not a scalable approach for the integration of other chains. One general pattern to allow accessing the state of other chains is to maintain a list of RPC provider services for a given chain and use HTTPS outcalls to interact with a random sample. Depending on the selection of the services and the size of the sample, there can be a high assurance of the valididty of the data if all services in the sample agree. However, with the recent development of the proof-of-stake beacon chain and the merge, there has been significant progress in the development of Ethereum light clients which allows an integration without having to trust the RPC providers. These light clients enable the verification of state and inclusion of events through the use of merkle proofs and the reliance on sync committees - a slowly changing (approx. 25h), random sample of 512 validators - to obtain block headers with BLS signatues, rather than requiring the validation of the entire blockchain. Areas for RFPs We'd like to encourage individuals and teams to explore the integration of Ethereum light clients as canisters on the Internet Computer to allow other canisters secure access to data from the Ethereum blockchain. The nascent Helios client, which is implemented in Rust, could provide a good starting point.

Jan 17, 2023
Read more from Dominic Wörner
Published on HackMD