What's New in v2.5?

TokenTable Suite v2.5 is the result of introspection and user feedback. No features have been dropped but the user interaction process and API have been massively simplified.

Here are the major changes compared to v2:

User Action	v2	v2.5
Creating new Presets and Actuals as a founder	The user can choose between a normal function or a batched function.	To eliminate confusion and API bloat, only the batched functions remain.
Enabling token streaming as a founder	The streaming setting applies globally to all unlocking schedules.	The streaming setting is applied individually to each unlocking schedule Preset.
Depositing funds as a founder	The user must call a deposit function and specify which exact unlocking schedule is the deposit going into, as the token pools for each token recipient are separate.	To eliminate complex frontend and contract interactions, all token recipients now claim from a shared pool of tokens. The deposit function has been eliminated and replaced with the native ERC-20 transfer function.
Withdrawing funds as a founder	The user must specify which exact unlocking schedule they are trying to withdraw from, for the same reasons as mentioned above.	The withdraw function is straightforward and only requires an amount.
Canceling schedules as a founder	There is no batch function. The user can also be blocked from canceling an erroneous schedule as it is required to fully reimburse the recipient at the moment of cancellation.	The function is batched by default. The user will no longer be blocked even if the recipient already has an unclaimed balance. The user can also choose to wipe the unclaimed balance in case the schedule was created by mistake but the unlocking process has already started.
Claiming unlocked tokens as a recipient	The user can choose between a normal function or a batched function.	To eliminate confusion and API bloat, only the batched functions remain.
Access Control Delegate vs. Hooks	There is little functional difference between the two. However, both exist and the user can set them separately.	Access Control Delegate has been removed as the same functionality can be achieved with Hooks.