It's just base64, you can decode it anywhere to see what's inside:

```

{

"proofs": [

{

"id": "0NI3TUAs1Sfy",

"amount": 1,

"secret": "6j5ONV6WKi9S+yZisfSh4ZAY/zinuwFBS0MVt+POoRA=",

"C": "032ff63ef3de8e658a2cecb35097e5a05ff61e6bf6cd7734509b6db08028ea2fc7"

},

{

"id": "0NI3TUAs1Sfy",

"amount": 4,

"secret": "1dbvH2y8SuAjvwgJ7WQUIkvtq2mNnuxBFxzDAMCYxvU=",

"C": "03cae481b6285c9dc963e11b17c1f6e1b74dc0928151f5463079e51846699472b2"

},

{

"id": "0NI3TUAs1Sfy",

"amount": 16,

"secret": "jask5B1i3Esrb5SXQ0vjQde+iOugoXbdD3S6lDTwvTY=",

"C": "0314224839a27a8be99aa7a08bcbb3dfa46d9269b5803bbf348a25cd2ab1cbb4b8"

}

],

"mints": []

}

```

And yes, someone will need to know the mint to get the tokens. Your mints field is not populated. If you add the URL into that field and re-encode it as base64, it should pull automatically when someone tries to receive.

Reply to this note

Please Login to reply.

Discussion

Oh interesting, looks like a bug. #[4] any idea what might be happening here?