stellar-expert / albedo Goto Github PK

Albedo seems to have issues on adding liquidity to tokens with Alphanumeric 12 when the name comes before other asset which is Alpha4.

Here is the LP:
curl https://horizon.stellar.org/liquidity_pools/13c2bc477497011061ff3c66f02c9fd66da5a892afa6acf8d65066f796f8aca5

The example is XCHF BTCLN. X is after B but BTCLN is Alphanumeric 12.

I think what is happening is
native goes before Alphanumeric 4 which goes before alphanumeric 12.

"Assets are not in lexicographic order" at https://albedo.link/wallet/liquidity-pool/deposit
Error: Assets are not in lexicographic order
    at new e (https://albedo.link/albedo.08119d92f546391a2361.js:2:1048924)
    at wt (https://albedo.link/albedo.08119d92f546391a2361.js:2:135223)
    at bt (https://albedo.link/albedo.08119d92f546391a2361.js:2:134887)
    at ie.get poolId (https://albedo.link/wallet.1f231791d6b1263d91e0abf3bb31f5e6.js:1:24244)
    at We (https://albedo.link/albedo.08119d92f546391a2361.js:2:607268)
    at e.t.computeValue_ (https://albedo.link/albedo.08119d92f546391a2361.js:2:605528)
    at e.t.trackAndCompute (https://albedo.link/albedo.08119d92f546391a2361.js:2:605372)
    at e.t.get (https://albedo.link/albedo.08119d92f546391a2361.js:2:604608)
    at e.t.getObservablePropValue_ (https://albedo.link/albedo.08119d92f546391a2361.js:2:632597)
    at ie.get (https://albedo.link/albedo.08119d92f546391a2361.js:2:637369)
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.110 Safari/537.36

Trying to use Albedo to make deposits into liquidity pools, founds few bugs, this is number 3

Trying to create liquidity pool that does not yet exist

Transaction fails

stellar.expert also doesn't show it correctly
https://stellar.expert/explorer/public/tx/e3470d700a9fb569a71205e5dfbe7c826399e6479e8c6bf88b3c1d2d42c0e39f

"Invalid asset name: undefined." at https://stellar.expert/explorer/public/tx/e3470d700a9fb569a71205e5dfbe7c826399e6479e8c6bf88b3c1d2d42c0e39f
TypeError: Invalid asset name: undefined.
    at new s (https://stellar.expert/distr/app.js?v=0.18.4:2:39736)
    at Function.parse (https://stellar.expert/distr/app.js?v=0.18.4:2:41144)
    at a (https://stellar.expert/distr/explorer.js:1:105112)
    at T (https://stellar.expert/distr/explorer.js:1:107917)
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.54 Safari/537.36

Issue description

Unable to sign using Ledger Wallets.

Steps to reproduce the issue

1. Connect to Ledger via Albedo
2. Default BIP Path checked
3. unable to create account

What's the expected result?

Able to create account

What's the actual result?

No error/feedback/account created

What I believe is going on/possible fix:

Currently unable to connect to Ledger wallets using default BIP path m/44'/148'/0'.
if you change to the paths from https://walletsrecovery.org/ -> m/49'|84'/0'/0' you can get albedo to recognize the ledger, however you are unable to sign anything. I'm assuming this is due to the fact that no account matching that path derivation exists on the ledger, and I'm unable to create an account matching that path using ledger live or any other tool.

Hey team, I was able to connect my ledger to Albedo. I was also able to signHash (sign text message on playground). However, I am unable sign any transaction using my Ledger Nano X. I have received the following errors (the first one while signing transaction on playground and the second one while using @albedo-link/intent to sign tx (albedo.tx()). I am able to sign using Stellar laboratory) -

Hey team, I am trying to connect to Albedo using my ledger nano X but it throws an error. I was able to connect to accountviewer on Stellar.
I was not able to connect using the chrome extension so I tried using the albedo.link where I got this error -
message: "Unable to claim interface." name: "TransportInterfaceNotAvailable"

In the playground I tried to show public key from account linked to trezor,
at first browser blocked "double" pop-up, but after I enabled it and confirmed hash on the device (which doesn't really tell user what's going on, so on-screen guidance would be very helpful)

Then it failed

On https://albedo.link/login I can't login on my mobile browser.
I have tried with both Opera and Firefox browser.
I'm able to import my accounts fine, but on this login screen, the Log In button doesn't become pressable after entering a password.
When pressing the enter/return/confirm button on the onscreen keyboard, an unhandled error pops up.
The behavious is the same in both Opera and Firefox browsers.

Transaction is made without memo, while memo is entered in transaction form

Reproduce:

1. Go to Transfer
2. Insert wallet and sum
3. Write text memo
4. Delete wallet address with select-all - backspace
5. Insert wallet again
6. Execute transaction

it should instead create the account and fund it

Trying to use Albedo to make deposits into liquidity pools, founds few bugs, this is number 2

When you choose assets for which liquidity pool exists but has 0 balances

"new BigNumber() not a number: 0aN" at https://albedo.link/wallet/liquidity-pool/deposit
BigNumber Error: new BigNumber() not a number: 0aN
    at ee (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:321134)
    at r (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:326614)
    at new V (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:319036)
    at M (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:108273)
    at Q (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:108055)
    at F (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:108843)
    at le (https://albedo.link/882.js:1:27260)
    at oa (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:798235)
    at Gs (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:850474)
    at Su (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:837680)
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.54 Safari/537.36

I ran into the following issue. I have a transaction that I want the user to sign, this transaction contains a CreateAccountOperation. If the pubkey is not present in the params given to the tx intent, things are displayed correctly. But I want to restrict the user to signing with a specific public key. When I set the pubkey param, Albedo starts loading and then shows a blank page.

I debugged it a bit and found that it is making a request to horizon for the account being created and of course, that returns a 404. This seems to be triggering the failure.

This is the info I'm using:

• xdr: AAAAAgAAAADWMDFohuQiZVyhhMYzYfnvFvzIqQvGQssoXRaFNQeycgAAAMgABcfNAAAAAAAAAAAAAAAAAAAAAgAAAAEAAAAA1jAxaIbkImVcoYTGM2H57xb8yKkLxkLLKF0WhTUHsnIAAAAAAAAAABsmKSe64xLVdnz/zobxnqpDmsEak+GLtGZaK7AnY0psAAAAAAX14QAAAAABAAAAABsmKSe64xLVdnz/zobxnqpDmsEak+GLtGZaK7AnY0psAAAABQAAAAAAAAAAAAAAAAAAAAEAAAACAAAAAQAAAAMAAAABAAAAAwAAAAEAAAADAAAAAAAAAAEAAAAA1jAxaIbkImVcoYTGM2H57xb8yKkLxkLLKF0WhTUHsnIAAAABAAAAAAAAAAA=
• pubkey: GDLDAMLIQ3SCEZK4UGCMMM3B7HXRN7GIVEF4MQWLFBORNBJVA6ZHFIJH
• network: testnet

Hi there,

I'd like to hear your thoughts on this feature request. With CAP38 and Turret-backed smart contracts coming to Stellar, some "clever" but not very descriptive operations will be happening, and it would be useful to show the user what they're all about via a bespoke description. The description should not replace the actual operation "Pay 100 XLM to G...1 from G...2", but it would be good if it could also be explained as "Pay 100 XLM to Company X for product A".

If this sounds feasible and reasonable, I'm also keen to explore helping out with the implementation if you can point me in the right direction.

Keen to hear your feedback.

Thank you!

I don't see how to add liquidity to a pool anymore.
The only option (I can find) is to withdraw liquidity.
Definitely NOT an improvement hiding the liquidity tab.

Hello,

we have just found an issue with albedo parsing a transaction XDR containing a CreateClaimableBalance operation.

Albedo show a wrong claimant destination address, you can view an example in the image below:

If needed I can post also the XDR transaction string

Getting this error trying to use the intent flow for a tx intent. Works fine in Chrome.

Please provide code which demonstrates how to use Albedo in the browser, and not server-side.

Your documentation indicates the following:

Alternatively, you can import the UMD build in the browser directly from UNPKG:

Please provide some code to show how I can use the publicKey function (from the albedo object that is provided in albedo.intent.js).

Is localization currently on the roadmap?

This is useful when integrating with Albedo, so that we could handle this case.

Uncaught TypeError: Cannot read property 'setItem' of null
    at Module.<anonymous> (albedo-contentscript.js:1)
    at s (albedo-contentscript.js:1)
    at Object.<anonymous> (albedo-contentscript.js:1)
    at s (albedo-contentscript.js:1)
    at albedo-contentscript.js:1
    at albedo-contentscript.js:1

I keep seeing these in my console every once in a while. This happens when Albedo is inactive (window is not open).

If you have multiple wallets sometimes it appears to cache the last wallet used. I have verified this on https://clpx.finance and https://lumenswap.io

https://user-images.githubusercontent.com/17188302/163555731-f7ba02d1-3442-44e1-834c-78c5bf660002.png

Hi all,

This is possibly me not understanding how it works, but I'd like to see if there's a workaround.

I am offering the user to sign a transaction that required 3 signatures; 2 signatures are already included and their signature is the third one.

The transaction consists of:

Main signatory account A
Main signatory account B

Issuer Account C (signed w/ main signatory account A)
Distributor Account D (signed w/main signatory account B)
User Account C

User C pays into Distributor Account D (2 payments)
Issuer Account pays into Distributor Account D
Distributor account D pays into User C

I am seeing that "More signatures are required" but the transaction goes through just fine. Is this the expected behaviour?

Here is the test XDR:

https://laboratory.stellar.org/#xdr-viewer?input=AAAAAgAAAABDt6sTdUhUkL%2BzdldE1gNS1NBnLun4K6sDFaOVJ%2BeWEQAAAyAABNboAAAAtwAAAAAAAAAAAAAACAAAAAEAAAAAH4InrCof9y5jJhLJdnhUH5PQUjVjiLwfDUlBxow3gDYAAAAGAAAAAlhUU0FSUwAAAAAAAAAAAAD%2BtBOh28Q8gg%2FXai72CIyzafowHwCf8bqYlAbcJULalAAAD9h0YwkBAAAAAQAAAABDt6sTdUhUkL%2BzdldE1gNS1NBnLun4K6sDFaOVJ%2BeWEQAAAAEAAAAAH4InrCof9y5jJhLJdnhUH5PQUjVjiLwfDUlBxow3gDYAAAACWFRTQVJTAAAAAAAAAAAAAP60E6HbxDyCD9dqLvYIjLNp%2BjAfAJ%2FxupiUBtwlQtqUAAAAAIt5kQAAAAABAAAAAB%2BCJ6wqH%2FcuYyYSyXZ4VB%2BT0FI1Y4i8Hw1JQcaMN4A2AAAABgAAAAJYVFNVU0RDAAAAAAAAAAAAYdNCcD5YFIcLTAcrVlZaeBsOllhsEuhB3f%2BWCpoXVNgAAAAbCwQS1gAAAAEAAAAAQ7erE3VIVJC%2Fs3ZXRNYDUtTQZy7p%2BCurAxWjlSfnlhEAAAABAAAAAB%2BCJ6wqH%2FcuYyYSyXZ4VB%2BT0FI1Y4i8Hw1JQcaMN4A2AAAAAlhUU1VTREMAAAAAAAAAAABh00JwPlgUhwtMBytWVlp4Gw6WWGwS6EHd%2F5YKmhdU2AAAAAAA7gmAAAAAAQAAAAAfgiesKh%2F3LmMmEsl2eFQfk9BSNWOIvB8NSUHGjDeANgAAAAYAAAACWFRBTkxQAAAAAAAAAAAAAH4Xu5kFY4ZsFShIpmVD6qqNNyKhsMVijE2ztm%2BqDb51AAABSzVIRuwAAAABAAAAAH4Xu5kFY4ZsFShIpmVD6qqNNyKhsMVijE2ztm%2BqDb51AAAAAQAAAAAfgiesKh%2F3LmMmEsl2eFQfk9BSNWOIvB8NSUHGjDeANgAAAAJYVEFOTFAAAAAAAAAAAAAAfhe7mQVjhmwVKEimZUPqqo03IqGwxWKMTbO2b6oNvnUAAAAAC2NY6AAAAAEAAAAAQ7erE3VIVJC%2Fs3ZXRNYDUtTQZy7p%2BCurAxWjlSfnlhEAAAAGAAAAAlhUQU5MUAAAAAAAAAAAAAB%2BF7uZBWOGbBUoSKZlQ%2BqqjTciobDFYoxNs7Zvqg2%2BdX%2F%2F%2F%2F%2F%2F%2F%2F%2F%2FAAAAAQAAAAAfgiesKh%2F3LmMmEsl2eFQfk9BSNWOIvB8NSUHGjDeANgAAAAEAAAAAQ7erE3VIVJC%2Fs3ZXRNYDUtTQZy7p%2BCurAxWjlSfnlhEAAAACWFRBTkxQAAAAAAAAAAAAAH4Xu5kFY4ZsFShIpmVD6qqNNyKhsMVijE2ztm%2BqDb51AAAAAAtjWOgAAAAAAAAAAt95hOIAAABAMzMiBWeQNPTW47CLdVSLadV1ygtchbjVlqqNxbiSKs7hXt6V0wL4PaktRoLQUMNlvBokO63A%2FvoM76p6HsuwAcZ6dvwAAABAkzJT5d8PDJ738b5tKBEh0VsJFnugByKqWMV0HZ8crszBM8EGjfd9NCu%2Fud9GOwlO2DNvM3RGbIMGzJUy4FzBDA%3D%3D&type=TransactionEnvelope&network=test

Thank you!

This trade operation look like:

Which is obviously incorrect: swapped into negative amount of tokens?

error

This URL has the following example: https://albedo.link/playground?section=public_key

albedo.publicKey({
token: 'vuEiDlijTCLdR8fqDHdfUQUUyVpVenVO2YGBrljh/Iw='
})
.then(res => console.log(res.pubkey, res.signed_message, res.signature))

I preceded that code with this script tag:

It displays the following error:
albedo.publicKey is not a function

The following code confirms that a Module named 'albedo' is accessible from albedo.intent.js:
console.log(albedo)

Please describe how I can access the publicKey function.

Hey, just an issue I spotted while trying it out.
I wasn't able to connect trezor from chrome extension at all. When you click connect (where it usually redirects to trezor hosted page) it just refreshes the page and nothing happens.

On the albedo.link itself I was able to link the account, but it threw CSP error

Hello,

I am trying to send XLM from albedo to a Bitstamp account.

When I confirm the transaction, the status of the transaction says "submitting transactions".

Unfortunately, the transaction is never processed and it is always saying "submitting transactions".

It could be due to a pop-up issue with IOS but I am not sure.

Do you know what I could do to finalize the transfer?

Thanks a lot!

Trying to use Albedo to make deposits into liquidity pools, founds few bugs, this is number 1

Choosing Asset A ETH:GBDEVU63Y6NTHJQQZIKVTC23NWLQVP3WJ2RI2OTSJTNYOIGICST6DUXR
Asset B USDT:GCQTGZQQ5G4PTM2GL7CDIFKUBIPEC52BROAQIAPW53XBRJVN6ZJVTG6V

Error details:
"Assets are not in lexicographic order" at https://albedo.link/wallet/liquidity-pool/deposit
Error: Assets are not in lexicographic order
    at new e (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:1045325)
    at mt (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:134480)
    at gt (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:134147)
    at ie.get poolId (https://albedo.link/882.js:1:23836)
    at We (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:605899)
    at e.t.computeValue_ (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:604159)
    at e.t.trackAndCompute (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:604003)
    at e.t.get (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:603239)
    at e.t.getObservablePropValue_ (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:631229)
    at ie.get (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:636001)
Components stack: 
    at u (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:582834)
    at t (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:891849)
    at t (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:892792)
    at de (https://albedo.link/882.js:1:32071)
    at t (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:891849)
    at t (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:892792)
    at div
    at u (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:582834)
    at pe (https://albedo.link/882.js:1:32356)
    at p (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:104248)
    at t (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:891849)
    at t (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:892792)
    at We (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:191458)
    at n (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:893324)
    at t (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:890200)
    at div
    at u (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:582834)
    at Je (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:192726)
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.54 Safari/537.36

I understand why this happens, but it may not be clear to users which asset should go first, therefore you might want to fix it and automatically sort assets instead of showing this error.

I am using just javascript. I am not using any "build system". The Albedo Chrome extension is active on my browser. My code is preceded with: <script src="https://unpkg.com/@albedo-link/intent/lib/albedo.intent.js"></script>

I was instructed to add the "default" indicator, as is shown below:

albedo.default.publicKey({
token: 'vuEiDlijTCLdR8fqDHdfUQUUyVpVenVO2YGBrljh/Iw='
})
.then(res => console.log(res.pubkey, res.signed_message, res.signature))

Although it is not displaying an error, it is not displaying the public key.

I also tried this approach (in an async function):
var objPublicKey = await albedo.default.publicKey()
console.log(objPublicKey)

It did not execute the "console.log" line. The program hung on "await albedo.default.publicKey()".

This problem was caused by the Chrome popup blocker. No other extensions use popups. You might want to consider using the extension sidebar instead, (which Chrome does not block as a popup).

Hello! 👋 I'd like to use Albedo on the Stellar test network, but I can't find a way how to fetch account info (get a public key) on testnet using @albedo-link/intent. I looked at the documentation and this repo but no luck (other methods have an option to set the network). Could you please point me in the right direction if I'm missing something? We'd like to add this to the Account Viewer. Thank you!

before update, theres option to sign transaction (so i can add another sign, before confirm it), its really useful to sign a transaction that need more 1 sign, now i need to copy XDR and add new sign in new page..

'passphrase' is misspelt twice.

I'm having the following issue. I'm trying to use the publicKey intent.

I'm getting the following output:

{
  "pubkey":"GDLDAMLIQ3SCEZK4UGCMMM3B7HXRN7GIVEF4MQWLFBORNBJVA6ZHFIJH",
  "signed_message":"GDLDAMLIQ3SCEZK4UGCMMM3B7HXRN7GIVEF4MQWLFBORNBJVA6ZHFIJH:24880b3aa7de51ac253277a1d48abbe187340f69395b020e0b5aca49c34b7072",
  "signature":"47fa0aba402e8698e156882bb498f7533ec30e711438a05d06f40fdc690342137ef22e86035242ad11b2773f810bd3ec8ff5c7b86532cbe70d7c181f3c77280f"
}

I'm trying to verify the signature but it always fails. I'm doing it in Rust, but even in node.js it is failing:

stellar = require('stellar-sdk')
key = stellar.Keypair.fromPublicKey('GDLDAMLIQ3SCEZK4UGCMMM3B7HXRN7GIVEF4MQWLFBORNBJVA6ZHFIJH')
signed_message = Buffer.from('GDLDAMLIQ3SCEZK4UGCMMM3B7HXRN7GIVEF4MQWLFBORNBJVA6ZHFIJH:24880b3aa7de51ac253277a1d48abbe187340f69395b020e0b5aca49c34b7072')
message_signature = Buffer.from('47fa0aba402e8698e156882bb498f7533ec30e711438a05d06f40fdc690342137ef22e86035242ad11b2773f810bd3ec8ff5c7b86532cbe70d7c181f3c77280f', 'hex')
key.verify(signed_message, message_signature) => false

I might be doing something wrong, but couldn't figure out what it is.

I've taken to deploying static sites via ViteJs recently but when including a .well-known stellar toml in the public directory I'm noticing CORS issues on Albedo. Other wallets seem able to resolve the toml just fine but Albedo is throwing this:

Access to fetch at 'https://nft.kalepail.com/.well-known/stellar.toml' from origin 'https://albedo.link' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

If I run the request in Albedo like this:
await fetch('https://nft.kalepail.com/.well-known/stellar.toml') it fails but if I run it like this:
await fetch('https://nft.kalepail.com/.well-known/stellar.toml', {mode: 'no-cors'}) it resolves just fine.

Is this something we'll always need a server to specifically set CORS headers or can you call the fetch request from your side in such a way as to successfully resolve the toml without me needing to set stuff on my end?

When trying to connect to StellarX, Aqua.network, and StellarTerm using the WalletConnect option continues to throw an error. I get the error using the website and browser extension. I have tried copying the QR code and pasting it to connect as well as screencap the QR and uploading it but neither option works. I keep getting the error "Failed to pair with dapp."

Description:	Debian GNU/Linux 11 (bullseye)
Release:	11
Codename:	bullseye

Brave Browser
[Version 1.46.153 Chromium: 108.0.5359.128 (Official Build) (64-bit)](https://brave.com/latest/)

Sign with the direct secret key is not working after the new UI update.

The signed_message parameter prepends the account pubkey: onto the message but the signature is only for the actual token. This is odd and unexpected. Either sign the whole message including the prepended account pubkey or drop the prepend. Either way whatever signed_message is is what the signature should match against. Otherwise you've gotta do some wonky splitting on the signed_message string.

I want to know if it's possible to use Albedo chrome extension with the testnet, thanks!

Currently the size of the main js bundle exceeds 1MB. Possible optimizations:

• Use preact instead of react
• Drop MobX dep in favor of centrzliaed state managed with react hooks
• Drop Trezor support (they don't want to fix things on their side)
• Use pure js version of the argon2 module if possible – wasm build is pretty huge
• Trim all unused code and cleanup data models

Looks like @ledgerhq/hw-transport-u2f has been deprecated. https://github.com/LedgerHQ/ledgerjs/blob/master/docs/migrate_webusb.md

I've noticed that the wallet supports only testnet and mainnet, but not futurenet. Are there plans to provide support for futurenet, given it's the only "test" network that allows for testing Soroban contracts?

Trying to use Albedo to make deposits into liquidity pools, founds few bugs, this is number 4

Created trustline to liquidity pool outside of albedo, now trying to see balances and the whole page crashes with

"Cannot read properties of null (reading '0')" at https://albedo.link/account
TypeError: Cannot read properties of null (reading '0')
    at d (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:270659)
    at oa (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:798235)
    at Gs (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:850474)
    at Su (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:837680)
    at Cu (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:837608)
    at Iu (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:837471)
    at mu (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:834458)
    at https://albedo.link/albedo.62186c4a6b59acf85160.js:2:784130
    at t.unstable_runWithPriority (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:941266)
    at Ko (https://albedo.link/albedo.62186c4a6b59acf85160.js:2:783907)
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.54 Safari/537.36

Hey there!

I love the functionality of the payment function Albedo does. Is there a plan on making a similar function for Claimable Balances?