attendCeremony() and acceptInvitation() functions can be invoked anytime. There should be a time constraint for these functions.

If there is no objection, the marriage has to be written to the blockchain.

• One of the spouses can change their mind during the ceremony (or before) and the marriage will be cancelled

The project requirements number 1: "two people decide to get married. They write it on a register, together with the date (day and time) of the ceremony, and the guest list"

If someone objects it should lead to failure. We need to implement some kind of state.

The project requirements number 5: "(optional) an objection will not cause an immediate failure, but a voting process will take place instead. The validity of the objection will be decided by the majority of the participants."

• A guest can be added only by a spouse
• Add this restriction to the addGuest() method

• The project requirements number 2: "any invited guest will accept or reject the invitation. In case of acceptance, a “ticket” will be released"
• For now the ticket is generated and released when a user is added to the guest list, this behaviour must be changed
• Check the date wheteher it is after the ceremony date or not. If so, give an error

The project requirements number 4: "a function will implement the sentence “if anyone has an objection to these two being married, speak now or forever hold your peace”. In case of any objection, the whole ceremony will stop and a failure will be registered on the blockchain. In the other case, the wedding will be written forever"

All finishing requirements for pushing the Wedding to the chain. Feel free to contribute to the commenting

The state of the contract must be stored. These states might be: not married yet, married, divorced, married objected...