v1.7.0 - Improved Function Naming and Event Tracking
·
40 commits
to main
since this release
🚀 Features
Breaking Changes
- Renamed Functions for Clarity:
transferFromBatch→transferFromRegulatedburnFromBatch→burnFromRegulated
New Features
- RegulatedTransfer Event: Added event emission for all regulated transfers, providing complete traceability
- Better alignment with ERC-1450 standard specification
Key Improvements
- Clearer function naming ("regulated" instead of "batch")
- Enhanced event tracking for compliance reporting
- Standard
transferFromnow clearly documented as always disabled
📝 Migration Guide
Update all function calls:
// Old:
transferFromBatch(from, to, amount, regulationType, issuanceDate)
burnFromBatch(from, amount, regulationType, issuanceDate)
// New:
transferFromRegulated(from, to, amount, regulationType, issuanceDate)
burnFromRegulated(from, amount, regulationType, issuanceDate)🔔 New Event
The RegulatedTransfer event is now emitted for all regulated transfers:
event RegulatedTransfer(
address indexed from,
address indexed to,
uint256 amount,
uint16 indexed regulationType,
uint256 issuanceDate
);Co-Authored-By: Claude noreply@anthropic.com
Full Changelog: v1.6.0...v1.7.0