TBD: Add the possibility of having multiple KYC providers for an STO instead of just one

[pabloruiz55]

[satyamakgec]

Yes, It should be

[sangheraio]

Yes will add this in. Closing as it is mentioned elsewhere

[pabloruiz55]

I believe you mean #47, but that refers to something else. Bypassing KYC provider vs having multiple KYC providers. Reopening but moving it to V2 milestone

[adamdossa]

This was mentioned as being an item which was needed for v1 (i.e. the 31st Jan mainnet deployment).

I think the most straightforward approach is to change KYC in Template.sol to be a fixed length array (say of size 10), and have the constructor take an array of valid KYC addresses.

SecurityToken can then receive this array from the chosen template and loop over these and turn them into a mapping for subsequent O(1) access.

@pabloruiz55 @Everhusk WDYT? This would be a minimal change that allows multiple (e.g. up to 10) KYC providers to be used for a single ST.