Python bindings for Farcaster.
The bindings are based on the protocol implementation by Hubble which can be found at @farcaster/hub-monorepo.
farcaster-py makes use of the gRPC interface exposed by farcaster hubs.
Until there is a proper pipy package, a quick and easy way to play around:
pip install farcaster-py
- Create
.env
with the following entries:
FARCASTER_HUB="farcaster_hub:grpc_port"
OP_ETH_PROVIDER="OP provider endpoint"
APP_FID="application fid"
APP_PRIVATE_KEY="application private key"
USER_FID="User fid"
USER_PRIVATE_KEY="User private key"
APP_SIGNER_KEY="You have to create a signer first. Use examples/approve_new_signer.py."
- Download the examples found in
examples/
and trypython ./get_user_casts.py
I have tried to both follow Farcaster's conventions and naming, but also provide a pythonic API that make sense to use without requiring deep knowledge of the underlying protocols.
The HubService
class uses Hubble's gRPC interface to interact with hubs. Most of the gRPC described in the protocol specification is avalable through farcaster-py.
Example:
from farcaster.HubService import HubService
hub = HubService(hub_address, use_async=False)
casts = hub.GetCastsByFid(fid=280)
for cast in casts.messages:
print(cast)
- Secure connections have not been implemented.
- 99% of the gRPC API is read-only: You get data from the hubs. The only (I think) call that allows you to change the global state is
HubService.SubmitMessage(Message) -> Message
. (see next section)
The Message.MessageBuilder
class offers three types of methods:
- The initializer that creates a new
MessageBuilder
with specific characteristics (hash scheme, signature scheme and the user's private key) - Methods like
MessageBuilder.link.add(...)
andMessage.link.remove(...)
that return aMessageData
protobuf. MessageBuilder.message(self, data: MessageData)
that getsMessageData
and hashes, signs, etc and returns aMessage
protobuf object ready to be used byHubService.SubmitMessage(Message)
Example:
from farcaster.HubService import HubService
from farcaster.fcproto.message_pb2 import SignatureScheme, HashScheme, Embed
from farcaster import Message
hub_address = '....'
app_signer = '....'
user_fid = '....'
hub = HubService(hub_address, use_async=False)
message_builder = Message.MessageBuilder(
HashScheme.HASH_SCHEME_BLAKE3,
SignatureScheme.SIGNATURE_SCHEME_ED25519,
bytes.fromhex(app_signer[2:])
)
data = message_builder.cast.add(
fid = user_fid,
text = "Hello, world!"
)
msg = message_builder.message(data)
ret = hub.SubmitMessage(msg)
The Signer
class provides a simple interface to creating signers.
To create a signer, you need:
- Fid and corresponding private key of the user that will approve the signer.
- The fid and private key of the application that will create and use the signer.
Once you have this data, you create a new Signer
, and use approve_signer()
to submit the on-chain tx:
# snippet from examples/approve_new_signer.py
s = Signer( op_eth_provider, user_fid, user_key, app_fid, app_key )
tx_hash = s.approve_signer()
signer_private_key = s.key
signer_public_key = s.signer_pub()
If you are installing from source, you use generate_proto.sh <HUBBLE VERSION>
to generate the corresponding protbuffer Python code.
./generate_proto.sh 1.5.6 git:main*
x schemas/
x schemas/gossip.proto
x schemas/hub_event.proto
x schemas/hub_state.proto
x schemas/job.proto
x schemas/message.proto
x schemas/onchain_event.proto
x schemas/request_response.proto
x schemas/rpc.proto
x schemas/sync_trie.proto
x schemas/username_proof.proto
Protobuf schemas parsed.
Eventually, farcaster-py will follow the version numbers of farcaster protocol buffers (when/if they become a separate package).
Until then, I'll keep version numbers low (0.0.x) and update them manually.
farcaster-py
is distributed under the MIT License.
This package was created and is maintained by @vrypan.eth.
An older repository, called hub_py has been a valuable source while building the initial version of farcaster-py
.