Which characteristics apply to Shared Allowance question.

Question

Options

• ASupport of account splitting
• BTight coupling between contracts
• CRequirement of counter dictionary
• DLoose coupling via sharing ID

• A
  79% (19)
• B
  8% (2)
• D
  13% (3)

Explanation

Shared Allowance is a smart contract pattern where a single token allowance is distributed across multiple accounts. Option A applies because the core mechanic splits one allowance among several participants, making account splitting fundamental. Option C applies because the contract must maintain a counter dictionary (a mapping/ledger) to track how much of the shared pool each participant has consumed.

B is wrong because Shared Allowance promotes loose coupling, not tight coupling - tightly coupled contracts depend directly on each other's implementation, which this pattern avoids.

D is wrong because "loose coupling via sharing ID" describes a different pattern (often called Shared ID or Reference-based patterns), where contracts coordinate by passing an identifier rather than splitting a balance pool.

Memory tip: Think of a shared pizza budget at a restaurant - you need a notepad (counter dictionary) to track who spent what from the shared tab (account splitting). Tight coupling would mean everyone is locked to the same waiter; Shared Allowance lets them order independently.

No community discussion yet for this question.