Cofer (@UseCofer) header
Cofer (@UseCofer) profile picture

Building shared-account infrastructure. @Robinhoodapp Chain. Community - https://teapaw.org/t.co/i2UoBr9yBc

telegram
Joined October 2026
Photo by Cofer (@UseCofer)Photo by Cofer (@UseCofer)Photo by Cofer (@UseCofer)Photo by Cofer (@UseCofer)Photo by Cofer (@UseCofer)Photo by Cofer (@UseCofer)Photo by Cofer (@UseCofer)Photo by Cofer (@UseCofer)Photo by Cofer (@UseCofer)Photo by Cofer (@UseCofer)
Your group chat already talks about money. Cofer gives it one shared account. Pool USDG, vote with your own key, buy Stock Tokens together. Anyone can leave with their exact share, any time. Coming soon on @RobinhoodApp Chain.
We're building Cofer as shared-account infrastructure on @RobinhoodApp Chain. Telegram is the initial interface. The account logic lives in contracts, with a separate signer and backend for proposals, transaction relaying and activity tracking. More coming.. 馃У
1
38
67
1,138
Does funding determine all later permissions? Putting money into a shared account and authorising its use are connected but distinct steps.
6
7
27
Why does an allowance need a period? An allowance gives a member permission within a defined amount and period.
21
24
95
What exactly does each approval cover? A vote needs to refer to a concrete payment: amount, recipient and any applicable conditions.
24
38
128
A passkey signature is useful because it binds a specific approval. Cofer's proposed Telegram flow should keep the signing decision connected to the conversation without confusing the two.
25
31
129
Join us now - t.me/usecoferonRH
The payment grew beyond the small-spend limit. Cofer's proposed larger-action path should follow the group's signing rules instead of treating available funds as an expanded allowance.
26
39
275
What exactly does each approval cover? Cofer is building a Telegram-facing group money account with bounded allowances and member signatures. Soon on @RobinhoodApp.
28
41
145
The payment grew beyond the small-spend limit. Cofer's proposed larger-action path should follow the group's signing rules instead of treating available funds as an expanded allowance.
1
26
1
33
284
A new deposit increases a balance. It does not explain every permission over that balance. Cofer's proposed account still needs its spending rules understood by the group.
26
33
148
A monthly allowance and a one-off approval answer different questions. Cofer is building a Telegram-facing group money account with bounded allowances and member signatures.
25
31
108
A monthly allowance and a one-off approval answer different questions. Cofer's shared-account design needs the period and amount visible before a member relies on either route.
27
35
189
The recipient changed after the group discussed the payment. That is a different action to inspect. Cofer's proposed signatures need to stay attached to the amount and destination actually being approved.
26
33
193
Cofer is being built around shared USDG with explicit rules for who may spend and when another collective decision is required.
1
2
Telegram remains the conversational interface. The signing step is where the particular action is authorised.
1
1
Depositing funds and approving their use are distinct events. Members should understand both.
1
A larger action follows the account's voting and signing rules. The existing allowance should not silently expand.
1
An allowance does not give a member ownership of the entire pot. It grants a bounded spending permission.
1
2
Small actions can use a defined allowance. The limit needs an amount and a period.
1
3
The proposed passkey flow asks members to sign the relevant decision individually.
1
2
A poll or message expresses a view. It is not automatically the signature the account requires.
1
2
12