HW05 Composer: Pocket money

Create a Business Network Archive (BNA) with the appropriate models, transactions, and access constraints that fulfill the requirements below. The BNA must have an initial transaction (setupHomework) that sets up a ledger state, where the fulfillment of each requirement can be demonstrated (assuming that the ledger is empty before the call of the initial transaction). Transactions that would dynamically add participants or assets are not needed, unless noted explicitly under the requirements, except the initializer transaction.

Please test your solution on Composer Playground before submission.

For every Participant and Asset type, the unique identifier must be a non-optional String field with the name id. The value of the field must conform to the following format: <TYPENAME>_<COUNTER>. For example, if we have a Participant type named User, then the id of the first created user must be USER_0, the id of the second user must be USER_1, etc.

Problem statement

Implement a BNA for giving a child pocket money.

Additional requirements:

Example scenario

Alice and Bob are partners, and Claire is their child. Alice and Bob have an initial account with 10 units. Alice puts in her salary of 3 units. Later, Bob withdraws 2 units for rent. Claire withdraws 1 unit to pay his classmate Dan to do his homework, but he'd like 2 units. Claire tries to withdraw another unit, but the withdrawal fails.

Transactions