Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider removing default shielding memo value #1392

Open
HonzaR opened this issue Feb 8, 2024 · 4 comments
Open

Consider removing default shielding memo value #1392

HonzaR opened this issue Feb 8, 2024 · 4 comments

Comments

@HonzaR
Copy link
Collaborator

HonzaR commented Feb 8, 2024

Is your feature request related to a problem? Please describe.

Current API:

    suspend fun shieldFunds(
        usk: UnifiedSpendingKey,
        memo: String = ZcashSdk.DEFAULT_SHIELD_FUNDS_MEMO_PREFIX
    ): Long
    /**
     * The default memo to use when shielding transparent funds.
     */
    const val DEFAULT_SHIELD_FUNDS_MEMO_PREFIX = "shielding:"

Describe the solution you'd like

Alternatives you've considered

Additional context

@HonzaR
Copy link
Collaborator Author

HonzaR commented Feb 8, 2024

@nuttycom We want to remove the default memo value in the shielding transparent funds API, even though it can be easily overridden with "". Is that correct? Thank you.

@nuttycom
Copy link
Contributor

nuttycom commented Feb 8, 2024

I'm not sure what this request was related to; allowing a memo when shielding is an important use case, so this shouldn't be a change at the level of the SDK. Shielding memos are well supported by zcash_client_backend.

@HonzaR
Copy link
Collaborator Author

HonzaR commented Feb 8, 2024

My question is only about the default string prefix of value of the memo parameter.

@nuttycom
Copy link
Contributor

My question is only about the default string prefix of value of the memo parameter.

I'm not sure where that convention came from; it certainly wasn't something that we discussed for ZIP 316.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants