You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please follow the template. Some things to consider:
Prototyping this is encouraged!
Which example app?
Should we limit the prover to 1GB and let it complete more slowly, or should we make a native wallet app that contains a browser? The answer is probably both but where should we start?
Can we make a more informed decision on the above by measuring first?
What can we measure before and after?
Would chunking to alower target circuit size be a good way to impose a memory limit?
Notes from offsite:
Team seems to have a slight preference for starting with a native wallet app. There is a UX impact, however. Please check in with product as a proposal emerges (before publishing RFC)
If we go with a native wallet app we should instead build a toolkit (i.e. extend the SDK) for native and empower the community to build the actual app
Note that native app is better when writing to Mina but less impactful when reading only
Estimates for native vs limiting memory are roughly equal with low certainty
The text was updated successfully, but these errors were encountered:
Please follow the template. Some things to consider:
Prototyping this is encouraged!
Notes from offsite:
The text was updated successfully, but these errors were encountered: