History

Jack Robison 1badc5f38c `BlockchainService` base class for readers and the writer -move base58.py and bip32.py into scribe.schema -fix https://github.com/lbryio/scribe/issues/3		2022-03-21 22:57:38 -04:00
..
types	initial	2022-03-08 12:41:51 -05:00
__init__.py	initial	2022-03-08 12:41:51 -05:00
attrs.py	`BlockchainService` base class for readers and the writer	2022-03-21 22:57:38 -04:00
base.py	initial	2022-03-08 12:41:51 -05:00
base58.py	`BlockchainService` base class for readers and the writer	2022-03-21 22:57:38 -04:00
bip32.py	`BlockchainService` base class for readers and the writer	2022-03-21 22:57:38 -04:00
claim.py	initial	2022-03-08 12:41:51 -05:00
compat.py	initial	2022-03-08 12:41:51 -05:00
Makefile	initial	2022-03-08 12:41:51 -05:00
mime_types.py	initial	2022-03-08 12:41:51 -05:00
purchase.py	initial	2022-03-08 12:41:51 -05:00
README.md	update readme	2022-03-15 23:57:42 -04:00
result.py	refactor handling blocked claims in serialization	2022-03-16 15:32:44 -04:00
support.py	initial	2022-03-08 12:41:51 -05:00
tags.py	initial	2022-03-08 12:41:51 -05:00
url.py	initial	2022-03-08 12:41:51 -05:00

README.md

Schema

Those files are generated from the types repo. If you are modifying/adding a new type, make sure it is cloned in the same root folder as the scribe repo, like:

repos/
    - scribe/
    - types/

Then, download protoc 3.2.0, add it to your PATH. On linux it is:

cd ~/.local/bin
wget https://github.com/protocolbuffers/protobuf/releases/download/v3.2.0/protoc-3.2.0-linux-x86_64.zip
unzip protoc-3.2.0-linux-x86_64.zip bin/protoc -d..

Finally, make should update everything in place.

Why protoc 3.2.0?

Different/newer versions will generate larger diffs and we need to make sure they are good. In theory, we can just update to latest and it will all work, but it is a good practice to check blockchain data and retro compatibility before bumping versions (if you do, please update this section!).