Further updates to documentation
This commit is contained in:
+2
-7
@@ -6,26 +6,21 @@ Basic Types of Plugins
|
||||
|
||||
While PluGeth has been designed to be versatile and customizable, when learning the project it can be helpful to think of plugins as being of four different archetypes.
|
||||
|
||||
.. contents:: :local:
|
||||
|
||||
RPC Methods
|
||||
-----------
|
||||
|
||||
this is a big ole test
|
||||
|
||||
|
||||
These plugins provide new json rpc methods to access several objects containing real time and historic data.
|
||||
|
||||
|
||||
Subcommand
|
||||
------------
|
||||
|
||||
A subcommand redifines the total behavior of Geth and could stand on its own. In contrast with the other plugin types which, in general, are meant to capture and manipulate information, a subcommand is meant to change to overall behavior of Geth. It may do this in order to capture information but the primary fuctionality is a modulation of geth behaviour.
|
||||
A subcommand redifines the total behavior of Geth and could stand on its own. In contrast with the other plugin types which, in general, are meant to capture and manipulate information, a subcommand is meant to change the overall behavior of Geth. It may do this in order to capture information but the primary fuctionality is a modulation of geth behaviour.
|
||||
|
||||
Tracers
|
||||
-------
|
||||
|
||||
Tracers rely on historic data recompiled after execution to give insight into a transaction.
|
||||
Tracers are used to collect information about a transaction or block during EVM execution. They can be written to refine the results of a ``debug`` trace or written to delver custom data using various other objects available from the PluGeth APIs.
|
||||
|
||||
Subscriptions
|
||||
-------------
|
||||
|
||||
Reference in New Issue
Block a user