In this commit, we increase the gRPC block size from 4MB to 50MB.
Recently, the output of lncli describegraph has hit the block size cap
due to the expansion of the mainnet graph. Without this attempts to
fetch the graph returns an error of:
[lncli] rpc error: code = ResourceExhausted desc = grpc: received message larger than max (4246753 vs. 4194304)
With this commit, we give ourselves some breathing room. It's important
to note that the max message size limit is a client side setting. As a
result, any developers driving lnd with gRPC will also need to raise
their block size limit as well if they wish to fetch the graph over
Hi u/quinsolo, thanks for tipping u/ReneFroger **400** satoshis!
*[^(More info)](https://www.reddit.com/r/lntipbot/wiki/index) ^| [^(Balance)](https://www.reddit.com/message/compose/?to=lntipbot&subject=balance&message=!balance) ^| [^(Deposit)](https://www.reddit.com/message/compose/?to=lntipbot&subject=deposit&message=!deposit 10000) ^| [^(Withdraw)](https://www.reddit.com/message/compose/?to=lntipbot&subject=withdraw&message=!withdraw put_invoice_here) ^| ^(Something wrong? Have a question?) [^(Send me a message)](https://www.reddit.com/message/compose/?to=drmoore718)*
What does this mean in terms of scalability of the network? What would it mean if 1 in every 10 coffee purchases in the world was made through LN? (With so many nodes having to connect)
I think they may need to have node groups to compress the topography (groups within groups) so you'd only need to know the topography within your own group. Is there such a thing already, or is it planned, or is it totally unnecessary?
gRPC is an open source remote procedure call protocol.
data is sent in some protocol between systems, in this case it's in gRPC messages. this is nothing to do with mined blocks.
source: systems engineer by day. crypto fighter by night!
Nothing to do with blockchain. It’s about how if you ask for information about all nodes and channels (the describegraph api call), then the response for mainnet is now larger than 4MB. Clients will reject the response but easily fixed by setting a config value larger than the default max response size of 4MB.
describegraph returns enough info to construct the network topography. More info: https://api.lightning.community/#describegraph
The config option I mentioned is a generic limit applied to all api calls.