diff --git a/css/app.33e3e4f6.css b/css/app.33e3e4f6.css new file mode 100644 index 0000000..ad752f9 --- /dev/null +++ b/css/app.33e3e4f6.css @@ -0,0 +1 @@ +pre[data-v-ce90be02]{background:#f4f4f4;border:1px solid #ddd;border-left:3px solid #f36d33;color:#666;page-break-inside:avoid;font-family:monospace;font-size:15px;line-height:1.6;margin-bottom:1.6em;max-width:100%;overflow:auto;padding:1em 1.5em;display:block;word-wrap:break-word} \ No newline at end of file diff --git a/docs/index.html b/docs/index.html index 57e84d0..78a6e98 100644 --- a/docs/index.html +++ b/docs/index.html @@ -124,7 +124,7 @@

A common convention in the Bitcoin web application ecosystem is for key management software (“wallets”) to expose their API via a JavaScript object in the web page. This object is called the common web wallet interface.

Historically, Provider implementations have exhibited conflicting interfaces and behaviors between wallets. This working group formalizes an Bitcoin extension API to promote wallet interoperability. The API is designed to be minimal, event-driven, and agnostic of transport and RPC protocols. Its functionality is easily extended by defining new RPC methods and message event types.

Historically, providers have been made available as window.bitcoin or window.webln in web browsers, but this convention is not part of the specification.

-

A list of current work in progress can be tracked from the issues tab in the playground repository, which includes a functional spec demonstration. A hosted instance of the demo can be found here together with the accompanying specification documentation.

+

A list of current work in progress can be tracked from the issues tab in the playground repository, which includes a functional spec demonstration. A hosted instance of the demo can be found here together with the accompanying specification documentation.