Jesus Najera

Super appreciate you noticing this - started randomly having issues a few weeks on a client app that has a chat feature that uses a fetch (previous conversation) & a...

Hey @will-at-stacks, just executed it on my end. All good, just needed a bit more time to read over the contract & then realized I had missed the first meeting...

Submitting for this track & officially revealing what we've been cooking up internally :) https://docs.google.com/document/d/1cuJbv_iCiXn80ByIcW7osLt346DDXqEKtbVhsxEN1sA/edit?usp=sharing

https://docs.google.com/document/d/1P1wPxQPxyUUDmQtOrkMCXE4I_NZ7C-YcT_REQG4NeQs/edit?usp=sharing Right here! Though scope has been changed since we decided to make this an auto-signing process.As opposed to both iOS & Android it's now either Android *or* RaspberryPI.

Issue closed with final SIP findings here: https://github.com/stacksgov/sips/issues/123

Discussing w/ ClarityWG it seems like the best / most practical solution here is to limit 'stack-increase' to users that are not straddling two signer-keys between upcoming cycles (aka they...

Did work over the weekend on this that can be found here: https://github.com/stacks-network/stacks-core/compare/feat/signer-key-amount-auth...feat/signer-key-amount-auth-stack-increase Reviewed with @hstove who'll 'git cherry-pick' commits into his main PR found here: https://github.com/stacks-network/stacks-core/pull/4461 I'll close issue...

Yeap @MarvinJanssen will do! Though atm this is on pause until at least EOM / Argon completion.*

Note: per the ClarityWG discussion on 2/27, this PR does NOT include a generated coverage file. There were a few issues in how & where it's generated so we're creating...

Removing Argon tag since this a conversation worth having but doesn't block Argon release, StackerDB trait not useful for anything off-chain stuff, do we want to expose this? Such as...