-
Notifications
You must be signed in to change notification settings - Fork 850
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WIP] Compact Filter protocol messages #548
base: master
Are you sure you want to change the base?
Conversation
Btw, are there already any serving full nodes on the mainnet? |
The only node on mainnet that I am aware of is the BTCD node that I myself am running. |
@MsBarber Is it merged to btcd already? Last time I checked it wasn't. In fact I'm looking at Roasbeef's btcd fork: https://github.com/Roasbeef/btcd is "This branch is 137 commits ahead btcsuite:master." Of course this may be something else. |
@nopara73 As far as I am concerned development has moved over to https://github.com/btcsuite/btcd I have a node running and have been sending cf related messages and getting appropriate responses. If you would like to connect to my node and give it a spin I would not mind sharing the IP, its mainnet. The BTCD node does take a good amount of time to sync if you chose to spin it up. |
Unsure as to why AppVeyor is having hard time locating the FilterType? |
There is also several warning to fix. |
Can you rebase and fix the build? |
1a58a6f
to
42392ae
Compare
@NicolasDorier Hey Nick, Appveyor seems to still be failing, however travis is passing. |
We use to say: the SQL is not broken. Take a closer look at the console log:
It compiles okay for all the targets except for net461. That's why it pass green in travis. Next, remove all the targets except net461 and build again, it has to fail. |
Just to make sure I cloned the repo following the instructions shown in the console log:
Then built the project with:
I expected to fail because I work on Linux and don't have .NET Framework. It failed and gave me the same error:
|
Ohhh it is simply that some files has the |
Lol, yes I also noticed this not too long ago and have applied the fix. Thank you so much for the help! Hmmm, is it necessary to have this wrapped in '#if !NOSOCKET'? I saw a mention of in #110 and it seems it was just to take care of some non portable IpEndPoint code. I am going to remove them and see if it builds, if so there is no need for them I think. |
Can you rebase? |
d52cef2
to
fab7b18
Compare
TravisCI was unable to located dotnet-sdk-2.1?
|
Retrying |
Can you add some tests? Is there some test vector in the BIP so we can try serializing and deserializing? |
878114e
to
24301c6
Compare
d114a5d
to
e4c0829
Compare
725a14b
to
bbcaf18
Compare
Hello, this is a work in progress for light client protocol messages. Still a WIP because of lack of proper tests. I would like to give credit to @lontivero for opening #401, getting the ball rolling on the issue, and giving me a solid place to start.
There has been a few changes regarding filter types, for now the only supported filter is "Basic". Therefore I have commented out the conditional checks for "Extended" filter type, also commented out the enum value.
For the payloads I have included all the fields included in bip157. I included the "length" fields which are technically not necessary to save in the object, as far as I am concerned.
I have overrode ToString() for testing purposes.
I appreciate all comments and feed back given.
The end goal is to eventually create a compact filter light client, similar to neutrino on top of Nbitcoin.