Bitcoin Forum
May 27, 2019, 02:49:20 AM *
News: Latest Bitcoin Core release: 0.18.0 [Torrent] (New!)
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: bip148 - binary builds in Gitian - segwit  (Read 360 times)
bincap
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
April 06, 2017, 05:24:51 PM
Last edit: April 13, 2017, 02:43:49 AM by bincap
 #1


EDIT(2017.04.13) website is live, https://bip148.org - see https://bitcointalk.org/index.php?topic=1867440.msg18567279#msg18567279



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512


I'm trying to help in testing proposal BIP148 for Bitcoin, by doing Gitian builds of that code.

Anyone wan to help SegWit and run a Gitian build too?

we build this tag:
https://github.com/magmaship/bitcoin/tree/v0.14.0-knotsbip148-rc1-INSECURE-TEST

This version makes your bitcoin node to from 2017 Aug start rejecting blocks that do not signal support for
Segregated Witness.

If enough people run this version, then
1) From August of 2017 all miners should at least signal support for future activation of SegWit  - otherwise their block will be rejected by your node right then from August, and if enough people do that then miners will be motivated to signal
2) Even before August 2017, your node will have user-agent version information that you do support this soft work (UASF) for segwit, causing more miners (and other users) to switch too

The code is NOT YET REVIEWED !!! this are experiments:
- - to see if our build infrastructure works fine
- - to possibly run this version on experimental nodes (do NOT run this on real node just yet, check in few days Smiley


Build (Gitian) results for me:
revision is 54893dab819ae50ab015aa3fcd54054f8c51a4db

sha256sum * | sort

00856236e3de42ea73fd9a8b9b8ace756847147242e7412995700085f1981b2d  bitcoin-0.14.0-win64.zip
1d362639c0c8e6eb463c16e390253fd644b1d707318ebee52fef71007d6f74af  bitcoin-0.14.0-win32.zip
2898430615896d0091ec8fe1560fc5c846be48b762a31bc37b6bce9b2f178b45  bitcoin-0.14.0-win32-debug.zip
313ad015e2c1589bcbc4e7d376453c2142d008ab334f31fa8f588bdd8f89e4d2  bitcoin-0.14.0-arm-linux-gnueabihf-debug.tar.gz
34f4ed38eea691ab3546956d4c2ad3df46e85d73ac2f48b79c7bfed2ed14a4a1  bitcoin-0.14.0-i686-pc-linux-gnu-debug.tar.gz
3854ae8affdb142fc42aa1edfcaa54325d69403909241dd0813e2399cb75e993  bitcoin-0.14.0-x86_64-linux-gnu-debug.tar.gz
43c9e0d32eb1a6c2b40e6d972dc14ab79d2c3d233f5e854f363e025d34e25a5b  bitcoin-0.14.0-x86_64-linux-gnu.tar.gz
458baa1140d9acefc8c7048ee36ed86e07b7cfc421c1b391c323f81c3b619f72  bitcoin-0.14.0-aarch64-linux-gnu.tar.gz
62185f9720ee9bd63c0c3cbc3d03243628f92080b0450fe03fcd5dcedf29a70b  bitcoin-0.14.0-aarch64-linux-gnu-debug.tar.gz
68c3d91061039fd663cca6e0d0bd8ad48e29dcb52bbf8fa1f96b71d4949d4031  bitcoin-0.14.0-osx-unsigned.dmg
71e0996ef30e249a8eba37669154dbce13cc9a63ec78504d3198ea8c83580f3a  bitcoin-0.14.0-win32-setup-unsigned.exe
a753419929562bb57545b6f0fe1e3a6897541653516fa4b7081375fbef97e262  bitcoin-0.14.0-win64-setup-unsigned.exe
b0e00d0fb675792ada4e20caa0bf1ff50254e5c704582cbc7382e17cede69e48  bitcoin-0.14.0-i686-pc-linux-gnu.tar.gz
c28ae75a67e176d6659a4a13fb12eaa3592eb8a9d47d3bb971cd257a0ed1d1e1  bitcoin-0.14.0-win64-debug.zip
ce0f6d7717d6b675568218d3c29c28fbfff79ce6a67927edb9b211c248bf8baf  bitcoin-0.14.0.tar.gz
ef85fbdc331ff333e1bebd5e2c5d990b7231f9575fb106dc8b61b60f977575e4  bitcoin-0.14.0-arm-linux-gnueabihf.tar.gz
fb70511298cf5087f54abefb6c60ddd4fb501f7a00d46a9c528313d4410f9d86  bitcoin-0.14.0-osx64.tar.gz

Regards, bincap (irc.freenode.org)
bitcoin: 19LXAG8Dd2Z2PW1MFf16mdU49fe6gXH2pN (secure hw wallet)
bitmessage: BM-2cUyGh9zHT3YYVtm77pZzmnvNDsnFL9sAJ
PGP: 755F 73E1 BFF9 A977 076E  5857 D708 974B 12C4 434F
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJY5nmyAAoJENcIl0sSxENPewkP/1b8Gnz9pI1xact/3f3entmU
28aB/ABPuBJJbo91ILw7EmYfdJ0ewOBn1549swMLWCWBs2Fd4cw5TpUurDHP6F85
KOynmIQ+Omfh7pnYY3zvpEWxFwKM8AmoeSZyY/PjV8GRFsEIe4SK+Crxro6sI4VN
GneF0AIgUFoWJHJQrFXYKOm+HbKX2raoVDkAegQJcJHBDUK6Rz94RsIkpW0O4XZh
mwNIuonXagBynww1q04LsaMHNNF422ymmUck/bYrjO4W5Qdfg6XZnK4NPIGSnox8
FtZ0nckaTpDNZ4l872/tYihq5gy1IgB+D20M3qSONpUhAYGGeor6PQJGNwaCH9J8
kNv6KqUVbllzdxV6FnbC/Awf+Ivd92iGcptcoQgMdLqei+gEzZhlO4rmGqiy7lHr
hj9MgJAOAsMieOzLKUcKpW4hUqwe61xqbmjngerC/uZXckczO6GDJNvzBpFfH3Kb
VqbIbJYtocR/1B/JgmnnONzvh61fnUSZbWCUdvWAy/7ihdy9lZ9gmCZ0dRdTpBUC
sl250ap9O6A1kmkBWjya7yBvECg8imCKYuCXB5JnEVK0kTbP+MaLj8xIqn1LOqS9
ISn2zy0zwDFaQYOb593RwJY1V70ok8Kg2VfpU+gKqambSiMIlMhDiaBd5285mwQh
LGe4oJCXJvVRWvki+NOy
=P+9q
-----END PGP SIGNATURE-----
1558925360
Hero Member
*
Offline Offline

Posts: 1558925360

View Profile Personal Message (Offline)

Ignore
1558925360
Reply with quote  #2

1558925360
Report to moderator
1558925360
Hero Member
*
Offline Offline

Posts: 1558925360

View Profile Personal Message (Offline)

Ignore
1558925360
Reply with quote  #2

1558925360
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1558925360
Hero Member
*
Offline Offline

Posts: 1558925360

View Profile Personal Message (Offline)

Ignore
1558925360
Reply with quote  #2

1558925360
Report to moderator
1558925360
Hero Member
*
Offline Offline

Posts: 1558925360

View Profile Personal Message (Offline)

Ignore
1558925360
Reply with quote  #2

1558925360
Report to moderator
jexphe2k
Newbie
*
Offline Offline

Activity: 42
Merit: 0


View Profile
May 30, 2017, 03:39:52 AM
 #2


EDIT(2017.04.13) website is live, https://bip148.org - see https://bitcointalk.org/index.php?topic=1867440.msg18567279#msg18567279



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512


I'm trying to help in testing proposal BIP148 for Bitcoin, by doing Gitian builds of that code.

Anyone wan to help SegWit and run a Gitian build too?

we build this tag:
https://github.com/magmaship/bitcoin/tree/v0.14.0-knotsbip148-rc1-INSECURE-TEST

This version makes your bitcoin node to from 2017 Aug start rejecting blocks that do not signal support for
Segregated Witness.

If enough people run this version, then
1) From August of 2017 all miners should at least signal support for future activation of SegWit  - otherwise their block will be rejected by your node right then from August, and if enough people do that then miners will be motivated to signal
2) Even before August 2017, your node will have user-agent version information that you do support this soft work (UASF) for segwit, causing more miners (and other users) to switch too

The code is NOT YET REVIEWED !!! this are experiments:
- - to see if our build infrastructure works fine
- - to possibly run this version on experimental nodes (do NOT run this on real node just yet, check in few days Smiley


Build (Gitian) results for me:
revision is 54893dab819ae50ab015aa3fcd54054f8c51a4db

sha256sum * | sort

00856236e3de42ea73fd9a8b9b8ace756847147242e7412995700085f1981b2d  bitcoin-0.14.0-win64.zip
1d362639c0c8e6eb463c16e390253fd644b1d707318ebee52fef71007d6f74af  bitcoin-0.14.0-win32.zip
2898430615896d0091ec8fe1560fc5c846be48b762a31bc37b6bce9b2f178b45  bitcoin-0.14.0-win32-debug.zip
313ad015e2c1589bcbc4e7d376453c2142d008ab334f31fa8f588bdd8f89e4d2  bitcoin-0.14.0-arm-linux-gnueabihf-debug.tar.gz
34f4ed38eea691ab3546956d4c2ad3df46e85d73ac2f48b79c7bfed2ed14a4a1  bitcoin-0.14.0-i686-pc-linux-gnu-debug.tar.gz
3854ae8affdb142fc42aa1edfcaa54325d69403909241dd0813e2399cb75e993  bitcoin-0.14.0-x86_64-linux-gnu-debug.tar.gz
43c9e0d32eb1a6c2b40e6d972dc14ab79d2c3d233f5e854f363e025d34e25a5b  bitcoin-0.14.0-x86_64-linux-gnu.tar.gz
458baa1140d9acefc8c7048ee36ed86e07b7cfc421c1b391c323f81c3b619f72  bitcoin-0.14.0-aarch64-linux-gnu.tar.gz
62185f9720ee9bd63c0c3cbc3d03243628f92080b0450fe03fcd5dcedf29a70b  bitcoin-0.14.0-aarch64-linux-gnu-debug.tar.gz
68c3d91061039fd663cca6e0d0bd8ad48e29dcb52bbf8fa1f96b71d4949d4031  bitcoin-0.14.0-osx-unsigned.dmg
71e0996ef30e249a8eba37669154dbce13cc9a63ec78504d3198ea8c83580f3a  bitcoin-0.14.0-win32-setup-unsigned.exe
a753419929562bb57545b6f0fe1e3a6897541653516fa4b7081375fbef97e262  bitcoin-0.14.0-win64-setup-unsigned.exe
b0e00d0fb675792ada4e20caa0bf1ff50254e5c704582cbc7382e17cede69e48  bitcoin-0.14.0-i686-pc-linux-gnu.tar.gz
c28ae75a67e176d6659a4a13fb12eaa3592eb8a9d47d3bb971cd257a0ed1d1e1  bitcoin-0.14.0-win64-debug.zip
ce0f6d7717d6b675568218d3c29c28fbfff79ce6a67927edb9b211c248bf8baf  bitcoin-0.14.0.tar.gz
ef85fbdc331ff333e1bebd5e2c5d990b7231f9575fb106dc8b61b60f977575e4  bitcoin-0.14.0-arm-linux-gnueabihf.tar.gz
fb70511298cf5087f54abefb6c60ddd4fb501f7a00d46a9c528313d4410f9d86  bitcoin-0.14.0-osx64.tar.gz
Hello Sir!

Regards, bincap (irc.freenode.org)
bitcoin: 19LXAG8Dd2Z2PW1MFf16mdU49fe6gXH2pN (secure hw wallet)
bitmessage: BM-2cUyGh9zHT3YYVtm77pZzmnvNDsnFL9sAJ
PGP: 755F 73E1 BFF9 A977 076E  5857 D708 974B 12C4 434F
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJY5nmyAAoJENcIl0sSxENPewkP/1b8Gnz9pI1xact/3f3entmU
28aB/ABPuBJJbo91ILw7EmYfdJ0ewOBn1549swMLWCWBs2Fd4cw5TpUurDHP6F85
KOynmIQ+Omfh7pnYY3zvpEWxFwKM8AmoeSZyY/PjV8GRFsEIe4SK+Crxro6sI4VN
GneF0AIgUFoWJHJQrFXYKOm+HbKX2raoVDkAegQJcJHBDUK6Rz94RsIkpW0O4XZh
mwNIuonXagBynww1q04LsaMHNNF422ymmUck/bYrjO4W5Qdfg6XZnK4NPIGSnox8
FtZ0nckaTpDNZ4l872/tYihq5gy1IgB+D20M3qSONpUhAYGGeor6PQJGNwaCH9J8
kNv6KqUVbllzdxV6FnbC/Awf+Ivd92iGcptcoQgMdLqei+gEzZhlO4rmGqiy7lHr
hj9MgJAOAsMieOzLKUcKpW4hUqwe61xqbmjngerC/uZXckczO6GDJNvzBpFfH3Kb
VqbIbJYtocR/1B/JgmnnONzvh61fnUSZbWCUdvWAy/7ihdy9lZ9gmCZ0dRdTpBUC
sl250ap9O6A1kmkBWjya7yBvECg8imCKYuCXB5JnEVK0kTbP+MaLj8xIqn1LOqS9
ISn2zy0zwDFaQYOb593RwJY1V70ok8Kg2VfpU+gKqambSiMIlMhDiaBd5285mwQh
LGe4oJCXJvVRWvki+NOy
=P+9q
-----END PGP SIGNATURE-----

Hello!

I have a question about this BIP148 upgrade for all BITCOIN running nodes and miners. If I have some BTC stored in say Keep Key BTC storage or a cold wallet the was printed a paper wallet...lets say I have stored them for 5 or 10 years and then decided to activated later, how would this kind of upgrade affect my stored BTC? Is BIP148 backward compatible? Would I still be able to get them back?

Best Regards,

Fidel Obando
achow101
Staff
Legendary
*
Offline Offline

Activity: 1778
Merit: 2406


bc1qshxkrpe4arppq89fpzm6c0tpdvx5cfkve2c8kl


View Profile WWW
May 30, 2017, 04:46:03 AM
 #3

Hello!

I have a question about this BIP148 upgrade for all BITCOIN running nodes and miners. If I have some BTC stored in say Keep Key BTC storage or a cold wallet the was printed a paper wallet...lets say I have stored them for 5 or 10 years and then decided to activated later, how would this kind of upgrade affect my stored BTC? Is BIP148 backward compatible? Would I still be able to get them back?

Best Regards,

Fidel Obando
Yes, BIP 148 is backwards compatible. All soft forks (including BIP 148) are backwards compatible and allow you to spend from transactions already in the blockchain. All hard forks will likely do this too since a hard fork that prevents people from being able to spend their money is not likely to gain enough traction to be activated.

Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!