[META] Make the Raiden Spec Alderaan Release Ready

[Dominik1999]

Get to a spec to be up-to-date with Alderaan

When we Release Alderaan on Mainnet we need a Raiden Spec, that is

• up to date, i.e. every information is correct according to the current code base of the Raiden Client, the Raiden Services and the Raiden Contracts
• a good read, i.e. we have examples of the data structure and the code that is used

Therefore, we need to make sure, that every chapter contains the correct information.

Overall:

• make the table of contents consistent
• start every chapter with an overview like in "Smart Contracts for Raiden Services", i.e. start with a general explanation and the goal
• ensure that every chapter has a consistent structure (start with overview or summary, then continue with ...)

Raiden Message Specification

• Raiden Message Specification has the correct data fields and tables, see e.g.Bring "Messages" section in spec up to date #327
• Raiden Message Specification has correct, consistent and easy to read descriptions and definitions
• Raiden Message Specification has a consistent example for the messages

Raiden Transport

• Make sure Raiden Transport has the correct information, data fields and tables, see Update transport spec for Alderaan #330
• Get help from at least one outsider to make this a good, consistent read

Raiden Network Smart Contracts Specification

• Make sure Raiden Network Smart Contracts Specification has the correct information, data fields and tables (coordinate with @karlb ) Make sure Raiden Network Smart Contracts Specification has the correct information, data fields and tables #253
• Get help from at least one outsider to make this a good, consistent read

Smart Contracts for Raiden Services

• Make sure Smart Contracts for Raiden Services has the correct information, data fields and tables (coordinate with @karlb ) Make sure Smart Contracts for Raiden Services has the correct information, data fields and tables  #254 and [SP 2] Update the Solidity files in the spec repo #255

Raiden Monitoring Service

• Make sure Raiden Monitoring Service has the correct information, data fields and tables (coordinate with @palango )

Raiden Pathfinding Service

• Make sure Raiden Pathfinding Service has the correct information, data fields and tables, see [SP 3] PFS: Add example messages #314 (coordinate with @palango )

Mediation fees

• Add information about mediation fees. See Document imbalance fees #251
• improve chapter, see [SP 3] Changes to mediation fees chapter #307

Raiden Mobile Wallet Specification

• Find out who is responsible for that chapter
• Delete chapter, since it is not longer maintained

Raiden Terminology

• Make sure Raiden Terminology has the correct information, data fields and tables (coordinate with)
• Delete every term from Raiden Terminology that is not used

[pirapira]

• The Solidity sources in spec repo needs to be updated. [SP 2] Update the Solidity files in the spec repo #255

[jomuel]

• The Solidity sources in spec repo needs to be updated. [SP 2] Update the Solidity files in the spec repo #255

@pirapira do you want to do this together with the other contract spec issues?

[pirapira]

Yep.

[Dominik1999]

@jomuel thank you for taking care of this. What is missing here? Can you try to update and check the tick boxes?

[jomuel]

Note on the Terminology section: Some terms that are not used in the spec, but common and useful, have been left in it. It is meant to be a glossary for the project after all, not just footnotes for the spec.