dbft: remove Timestamp() API from dbft.ChangeView interface

This API is unused by dBFT. If a user needs to access ChangeView timestamp, he has to convert dbft.ChangeView to the user-defined ChangeView implementation. A part of #84. Signed-off-by: Anna Shaleva <[email protected]>
nspcc-dev · Mar 6, 2024 · 32e1df2 · 32e1df2
1 parent f3de891
commit 32e1df2
Show file tree

Hide file tree

Showing 3 changed files with 0 additions and 9 deletions.
diff --git a/change_view.go b/change_view.go
@@ -5,9 +5,6 @@ type ChangeView interface {
 	// NewViewNumber returns proposed view number.
 	NewViewNumber() byte
 
-	// Timestamp returns message's timestamp.
-	Timestamp() uint64
-
 	// Reason returns change view reason.
 	Reason() ChangeViewReason
 }
diff --git a/internal/consensus/change_view.go b/internal/consensus/change_view.go
@@ -41,11 +41,6 @@ func (c changeView) NewViewNumber() byte {
 	return c.newViewNumber
 }
 
-// Timestamp implements ChangeView interface.
-func (c changeView) Timestamp() uint64 {
-	return secToNanoSec(c.timestamp)
-}
-
 // Reason implements ChangeView interface.
 func (c changeView) Reason() dbft.ChangeViewReason {
 	return dbft.CVUnknown

diff --git a/internal/consensus/message_test.go b/internal/consensus/message_test.go
@@ -156,7 +156,6 @@ func TestPayload_Setters(t *testing.T) {
 	t.Run("ChangeView", func(t *testing.T) {
 		cv := NewChangeView(4, 0, secToNanoSec(1234))
 
-		assert.EqualValues(t, secToNanoSec(1234), cv.Timestamp())
 		assert.EqualValues(t, 4, cv.NewViewNumber())
 	})