Public contracts on project:Dabl


How would we go about disclosing contracts to the public party?

Should we fetch this public party on the front end, and then pass it in as a choice param while creating a contract so they can be made observer on the new contract?

1 Like

Hey Manish,

You’re exactly right. The public party can be fetched from an application’s frontend by querying GET [ledgerId] (remember to substitute your real ledgerId on the subdomain).

This will return the party identifiers in JSON format for two special parties, Public and UserAdmin (the latter of which can be used as an operator party for your application). You can then supply the public identifier as a parameter when creating a contract that has a public : Party field (as an example).

The public party is also available through the project:DABL ledger UI - every party selector dropdown will have the Public party as an option when filling in contracts.

1 Like

Thank you Alex

1 Like

Hi Alex thank you for your reply.
I wonder how we can get the token of the public party as well during running time?

1 Like

Hey @Med_Amine_ID

There are three ways of adding in the public party token.

  1. Directly, you can make a request to POST[:ledgerId]/public/token (documented here)

  2. If you’re creating a React-based UI, you can use this Daml Hub UI helper library @daml/hub-react - npm to create a <PublicLedger/> ledger context. Then you can use React binding equivalents to stream publicly viewable contracts.

  3. The token can also be copy/pasted from the Users tab in Daml Hub, though this is of somewhat limited use due to 24 hour expiry of tokens. But, for completeness, I figured I’d throw it out there.


Hi it’s still a little bit confusing for me.
Could you please share an example of an existing code ?

1 Like


If you’re using React, you can make use of some contexts from the aforementioned helper library. Install it in your project by running npm install @daml/hub-react

This example is for illustrative purposes, and I doubt will be directly copy-pastable, as it depends on how you’ve structured the rest of your app. But hopefully it will demonstrate the general pattern that you can integrate into your app.

In your app, you will likely have an App component that wraps the application in a


context, which provides the Daml bindings as hooks to the children components.

If so, you’ll want to wrap your application in some additional contexts. An App.tsx might look something along the lines of

// App.tsx 

import React from 'react'

import DamlLedger from '@daml/react'
import { PublicLedger, WellKnownPartiesProvider, useWellKnownParties } from '@daml/hub-react'

import { ledgerId, httpBaseUrl } from '../config'

import MainScreen from './MainScreen'

 * React component for the entry point into the application.
const App: React.FC = () => {
  return (
    <div className='app'>
        token={/* user's auth token */}
        party={/* user's party id */}

const PublicProvider: React.FC = ({ children }) => {
  // This component fetches the public party ID and uses it to instantiate a PublicLedger context
  const { parties, loading } = useWellKnownParties();

  if (loading || !parties) {
    return <div>Loading...</div>

  return (
      { children }

export default App;

Inside the MainScreen component, you’ll be able to use public streaming hooks, like so.

// MainScreen.tsx

import React from 'react'

import { useStreamQueriesAsPublic } from '@daml/hub-react'
// import your template from @daml.js/.../ 

const MainScreen: React.FC = () => {
  const allPublicContracts = useStreamQueriesAsPublic(MyPublicTemplate);

  return (
    <div className='main-screen'>
      { /* display public contracts */}
      { => <p>{c.contractId}</p>) }

export default MainScreen;

I hope this helps you get started!


Thanks for your reply.
we had tried @daml/hub-react but we are facing an issue while using useStreamQueriesAsPublic.
useStreamQueries works fine and I upgraded to version 1.11.1

(alias) namespace ClientProject
(alias) const ClientProject: damlTypes.Template<ClientProject, ClientProject.Key, "a632bd8c1ac26369271261732332aa9681d4b048233820d021df67c099072c6b:Main:ClientProject"> & {
import ClientProject
Argument of type 'Template<ClientProject, Key, "a632bd8c1ac26369271261732332aa9681d4b048233820d021df67c099072c6b:Main:ClientProject"> & { Archive: Choice<ClientProject, Archive, {}, Key>; ... 7 more ...; ProposeSubmission: Choice<...>; }' is not assignable to parameter of type 'Template<object, unknown, string>'.
  Type 'Template<ClientProject, Key, "a632bd8c1ac26369271261732332aa9681d4b048233820d021df67c099072c6b:Main:ClientProject"> & { Archive: Choice<ClientProject, Archive, {}, Key>; ... 7 more ...; ProposeSubmission: Choice<...>; }' is missing the following properties from type 'Template<object, unknown, string>': sdkVersion, keyEncode, encodets(2345)

1 Like

Hey @Med_Amine_ID , I just published @daml/hub-react to v0.2.0, which should be compatible with Daml 1.11.1

Let me know if the issue persists after upgrading!

1 Like

We had run into some issues.
I updated @daml/hub-react to 0.2.0 and still getting the same error.

const clientProjectAssets = useStreamQueriesAsPublic(ClientProject).contracts;


...Main:ClientProject”> & { ...; }' is missing the following properties from type ‘Template<object, unknown, string>’: sdkVersion, keyEncode, encode

without public: useStreamQueries(ClientProject) works fine, using the old lib: { useStreamQueries } from “@daml/react”;

1 Like

I’m unable to reproduce this issue with my project’s package.json set to the following versions:

"@daml/hub-react": "^0.2.0",
"@daml/ledger": "1.11.1",
"@daml/react": "1.11.1",
"@daml/types": "1.11.1",

Have you tried clearing your node_modules and reinstalling the dependencies? The old package might still be cached somewhere. Try the following within your project’s UI directory.

For npm:

$ rm -rf node_modules package-lock.json
$ npm install

For yarn:

$ rm -rf node_modules yarn.lock
$ yarn install
1 Like