|
(I'll accept that @franky1 - thanks for keeping it down to a single point)
That been said - then why do you think Russia is now trying to ban Bitcoin?
(again please try and keep your reply concise)
|
|
|
|
How much money satoshi owns I think it's irrelevant. In the long term, it's impossible that the governments are going to remain neutral or even "nice" towards Bitcoin. As soon as Bitcoin starts being relevant in the big picture (right now 6 billion dollars is nothing) they will attack, Bitcoin distribution being irrelevant. What they are not going to allow is to see how Bitcoin grows while fiat crashes. So let's get ready for the attack is all im saying, and best we can do to be ready is keep supporting Core devs, we need stability.
Let's not go there (you just invited in the trolls whose posts now I'm having to delete). This is not a "core vs. others" topic - so those with silly agendas please butt out - stick to the topic and no excess rubbish. |
|
|
|
Most Bitcoin enthusiasts are anti-government & anti-state. Many militantly so.
Governments can't control or issue BTC. Why in the world would governments be interested/supportive of Bitcoin? Seems pretty counterintuitive.
Maybe so - but with the GFC (and the possible soon repeat of it as they fixed nothing after 2008) I think that governments (and maybe even more their citizens) are aware of the risk of fiat and are looking for better assets (a major reason why housing prices are still soaring in much of the world now). |
|
|
|
|
An interesting point - I have always thought that Satoshi was not a single individual but instead a small group (probably only a few people though).
The fact that Satoshi disappeared around the time that Gavin visited the CIA may or may not have anything to do with anything - but I am mostly talking about "perceptions" rather than "realities" (as we may never know for sure).
Governments are typically rather coy when it comes to making accusations about other governments (that are not generally useful for local political consumption) as it tends to get in the way of things like "free trade agreements".
|
|
|
|
|
I am making this topic self-moderated to avoid nonsense posts but I won't delete any reasonable arguments on either side of this question (and yes it is my decision what is reasonable in this topic - if you don't like that then please create your own topic - it isn't that hard after all).
So - although we are seeing some governments accepting Bitcoin as having a role we are seeing others basically trying to ban it outright (Russia being the current example of this).
I wonder if part of the problem is the perception (however likely or not) that Satoshi is aligned with (or was the creation of) a government and therefore the Satoshi *stash* effectively belongs to that government (which is estimated at around 5-10% of all bitcoins).
To me it makes some sense that a country might fear that if Bitcoin were to be adopted as a "new gold" then if it turns out that one country already has 5-10% of the new gold standard then that would be a "hard pill to swallow".
I'm not advocating for "deleting Satoshi's stash" but simply raising the question that if we are wanting Bitcoin to be Gold 2.0 then perhaps this issue cannot just be disregarded.
(and no - this is not "Satoshi envy" from myself and also I think it is perhaps good to discuss something other than the block size)
|
|
|
|
One of the good things about having a project as large as this one is that when you get bored working on one thing there are many other things you can work on to keep your motivation going. Today's bit of fun for me was to extend the console user input behaviour to support a single key "choice" from a set of options. A console user input line begins with an ampersand character (&) with what follows typically being in the following form: When executed by a CIYAM console the above would prompt the user with: and the user would type in the value and press enter (even if standard input was redirected from a file this would be direct console input). But let's say we wanted the user to decide whether or not to continue something. It would be nice to just be able to type a simple 'y' or 'n' character (with no need to hit an Enter key) and this is what the "choice" addition I made today allows. Here is an example of what you would put into the console script: &Continue? [yes=1!Yes|no=!No] (choose one)
When the console command handler reads this you'll see the following output to the console: Continue? [y]es, [n]o (choose one)
Assuming you hit 'y' then the above line would instantly change to this: And the actual "command" issued would be this: which then could be used with say an @ifdef conditional such as the following: @ifdef $Continue
#we are continuing...
@else
#we are not continuing...
@endif
Obviously extending the console conditional handling to check values (rather than just whether empty or not) is something that will need to be added in order to make this new feature more usable but that will have to wait for another day when I'm bored.  |
|
|
|
|
Most of the online ones that I have played with have bugs (including those linked) so don't rely on them for anything very important.
Best to play with Bitcoin using "-regtest" for prototyping of actual scripts (the debug.log can help with working out why scripts have failed).
|
|
|
|
|
One of the first things that I learned as a professional software engineer was to "ignore the comments" as they were generally out of sync with the code (sometimes completely so).
Unfortunately if you want to understand software you need to actually be able to read software - sorry (for protocols other than Bitcoin there are RFC's but am pretty sure they will not be much easier to read than code for your average Joe either).
|
|
|
|
|
Nice article and very relevant to the current situation.
|
|
|
|
|
PGP (or GPG) can be used to encrypt private keys for offline wallets (the CIYAM Safe uses this technique) but if you are using an encrypted wallet with Bitcoin then there is no need to do any further encryption.
(so its usefulness is basically outside of Bitcoin)
|
|
|
|
With BIP66, all parts of BIP62 should be fixed (except those where the malleability comes from ECDSA signatures, but those aren't relevant here as it's the sender who strives for the txid remaining the same and no one else could be affected).
I think the main issue would be if the forked alt has not updated its tx signing code (as the sender's txid could be changed without their knowledge). By this I am referring to the low S values issue which I patched for CIYAM here: https://github.com/ciyam/ciyam/blob/master/src/crypto_keys.cpp#L531Other than that I think that using P2SH (rather than the original multisig) is just a neater approach (it probably doesn't alter the workflow though). |
|
|
|
Seems we are doing very similar things: https://bitcointalk.org/index.php?topic=1340621.0 (also based upon TierNolan's basic idea but reworked to use CLTV with P2SH so no malleability issues and txs should be considered as "standard" for both Bitcoin and Litecoin now). If you would like to use some of the CIYAM code to get your implementation using CLTV and P2SH you would be welcome to (also feel free to PM me if you wish to discuss it). Also if you are doing a GUI then with some very minor tweaks you could get it to work with AT blockchains as well (Qora and Burst) as they have supported ACCT for a long time now. |
|
|
|
A neat video - probably wouldn't have watched it if not for this topic so thanks. (although probably still a bit too abstract an explanation for those who don't get math very well) Reminds me of an idea I had many years ago which was to create a series called "The Secret Life Of Software" that would show how software algorithms worked by using very easily understood real-world illustrations/simulations. |
|
|
|
Further progress has been made with the new Trade package (it's nearing functional completion) and with the help of four other batch/script files to use Bitcoin with the "-regtest" (with one of four different wallets) the following script https://github.com/ciyam/ciyam/blob/master/src/bct_acct_test.cin simulates an ACCT between two users. In order to turn this into a usable decentralised exchange platform the Wallet package will need to be enhanced to perform the functionality that is being done manually through the CIYAM script. |
|
|
|
To elaborate on the workflow that would be involved in trading LTC for BTC: - Alice creates an LTC / BTC offer pair using the Trade web application (as this could be done once for many trades it won't be counted as a step).
- Brian clicks on the offer and then creates a Trade Transaction providing an Amount, an LTC Refund Address, a BTC Receive Address and a hashed Secret.
- Alice is notified she has a new Trade Transaction and supplies her BTC Refund Address and LTC Receive Address.
- Brian is notified that the deal is on and now sees a P2SH LTC Address which he sends the LTC funds to.
- Alice detects that Brian has sent the LTC funds (via a "watch address") and sends her BTC funds to a BTC P2SH Address.
- Brian now copies and pastes the BTC P2SH Redeem script into a special Wallet and redeems the BTC (disclosing the secret).
- Alice detects (via a "watch address") that Brian has redeemed the BTC and then discovers the secret from the redeem tx.
- Alice copies and pastes the secret and the LTC P2SH Redeem script into a special Wallet and redeems the LTC.
Number of steps for Alice (apart from creating the offer) is four whilst the number of steps for Brian is three (guess it should be slightly easier for the party that "goes first"). Note that if the Wallet is clever enough then perhaps Alice's second last step can be simply automated (i.e. the last two steps could be combined into one) but I think three steps each is about as good as it can get with this design. |
|
|
|
A decentralized exchange with a good interface would be quite useful for many. Can it do the reverse? e.g. BTC for LTC?
Yes - it would support that (just using the CIYAM software). I presume this related to the CHECKLOCKTIMEVERIFY and the check <data1> against <sig1> questions....I haven't looked at the code above yet.
Indeed - that is how it operates. Congrats on getting it working. Why do you think you've wasted your time?
Thanks - well - when it is done using AT instead then it will be integrated into a wallet and not have many steps (so ACCT between QORA and BURST should be a good experience). As CIYAM's blockchain is still a "work in progress" I would have to release Trade as a web application requiring therefore a separate Wallet application to operate with it (which is what my testing is emulating). That adds a few steps (copying and pasting) which I think is not going to be viewed very enthusiastically. Also when it comes to using Bitcoin (or even Litecoin) you could not realistically be expecting to do trades in under an hour or so (because time stamps in blocks are just not that accurate and you would need to wait for at least one confirmation between each step). |
|
|
|
So using the CIYAM Trade application along with using a CIYAM console acting as a Bitcoin/Litecoin wallet I demonstrated to my wife how you could exchange LTC for BTC without a 3rd party (or fees other than tx fees) and apparently it was so boring she fell asleep. Generating a spendable amount of RHS for "user1"...
Generating a spendable amount of LHS for "user2"...
Login as "user1" and create a Trading Pair (with Maximum Amount as at least 25) and then Logout.
Now login as "user2" and create a tx from the offer in the All Open Offers list with the following details:
Sending Amount: 25
Refund Address: mtW4pzRHXwNwkHa2mdy2EokKy5GZ4aMWtu
Receiving Address: mkoJtKoxHmdL8aXJvPudmUgZKC1xXHb9KT
Secret Hash: 2bb80d537b1da3e38bd30361aa855686bde0eacd7162fef6a25fe97bf527a25b
Now login as "user1" and edit the Trade Transaction in the My Trade Transactions list with the following:
Refund Address: mids4AKKn42KmcJTvaynUzmnhWnmfgwRMw
Receiving Address: mgF67ucKz7CddjuJwDvDUgC5HiJBRDGNBx
Now login as "user2" and from the tx click on the Waiting tx and copy and paste the Sending Address:
USER2_P2SH=2N1dPcqdkNyfNqysHDqWRq8hqSs6sT91LTP
Now "user2" will send LHS to their P2SH address.
Now login as "user1" and from the tx click on the Waiting tx and copy and paste the Sending Address:
USER1_P2SH=2NFtwQWeiQzMgeidPCrZZhATv6ULXqA8WaB
Now "user1" will send RHS to their P2SH address...
[
{
"involvesWatchonly" : true,
"account" : "user2 (user1's p2sh)",
"address" : "2NFtwQWeiQzMgeidPCrZZhATv6ULXqA8WaB",
"category" : "receive",
"amount" : 25.00000000,
"vout" : 1,
"confirmations" : 4,
"blockhash" : "55647bfcc1ea60124e3e358a046a1e6494babb666d656aec3a9ad7ea3b179e71",
"blockindex" : 1,
"blocktime" : 1453733457,
"txid" : "1b0effc3dbb318d988c5f8f3525c1e79fec7f327aebbc2028274361139042870",
"walletconflicts" : [
],
"time" : 1453733457,
"timereceived" : 1453733475
}
]
Now enter the following from the transaction information above:
TXID=1b0effc3dbb318d988c5f8f3525c1e79fec7f327aebbc2028274361139042870
VOUT=1
Now login as "user2" and from the tx click the Receive Checked button and paste the Secret Reveal Script:
SCRIPT=76a8202bb80d537b1da3e38bd30361aa855686bde0eacd7162fef6a25fe97bf527a25b87637576a91439f079037b44caa047b19f66f9446ad29ca1835888ac6704d0dea656b17576a9142
236ea542963ca5022db4332cd63aa2ed895af6888ac68
0100000001702804391136748202c2bbae27f3c7fe791e5c52f3f8c588d918b3dbc3ff0e1b01000000d44730440220456e9d366d89034c7321a900f17e60506cb9e6fb3c280587301609fda6af65
8502206d785719bc42de81ce05ac4b461fc9d4aab5286d4ec3ef8d0589ab3ed1076d7501210334ae38e2f6331bfc4832893edd540377bcfc08b1a63730339b91cf8a6e0b6636067365637265744c
6176a8202bb80d537b1da3e38bd30361aa855686bde0eacd7162fef6a25fe97bf527a25b87637576a91439f079037b44caa047b19f66f9446ad29ca1835888ac6704d0dea656b17576a9142236ea
542963ca5022db4332cd63aa2ed895af6888ac68000000000100f90295000000001976a91439f079037b44caa047b19f66f9446ad29ca1835888ac00000000
Now "user2" will redeem RHS from the "user1" P2SH address tx (exposing their secret).
Balance of RHS for "user2" is:
25.00000000
Now login as "user1" and from the tx click the Receive Checked button and paste the new Check Address:
ADDR=mkoJtKoxHmdL8aXJvPudmUgZKC1xXHb9KT
[
{
"involvesWatchonly" : true,
"account" : "user1 (user2's reveal)",
"address" : "mkoJtKoxHmdL8aXJvPudmUgZKC1xXHb9KT",
"category" : "receive",
"amount" : 25.00000000,
"vout" : 0,
"confirmations" : 1,
"blockhash" : "5ea97dcb1e76ca90ef0b71aae2208488df5d8344248be2713fbb8f1bae8a1667",
"blockindex" : 1,
"blocktime" : 1453733502,
"txid" : "d374d12b0cee799e7d3b233332b87ae41f18ffae9c1a5dc49f7436df4f216fcf",
"walletconflicts" : [
],
"time" : 1453733502,
"timereceived" : 1453733536
}
]
Now copy and paste the secret reveal txid:
TXID=d374d12b0cee799e7d3b233332b87ae41f18ffae9c1a5dc49f7436df4f216fcf
{
"txid" : "d374d12b0cee799e7d3b233332b87ae41f18ffae9c1a5dc49f7436df4f216fcf",
"version" : 1,
"locktime" : 0,
"vin" : [
{
"txid" : "1b0effc3dbb318d988c5f8f3525c1e79fec7f327aebbc2028274361139042870",
"vout" : 1,
"scriptSig" : {
"asm" : "30440220456e9d366d89034c7321a900f17e60506cb9e6fb3c280587301609fda6af658502206d785719bc42de81ce05ac4b461fc9d4aab5286d4ec3ef8d0589ab3
ed1076d7501 0334ae38e2f6331bfc4832893edd540377bcfc08b1a63730339b91cf8a6e0b6636 736563726574 76a8202bb80d537b1da3e38bd30361aa855686bde0eacd7162fef6a25fe97bf5
27a25b87637576a91439f079037b44caa047b19f66f9446ad29ca1835888ac6704d0dea656b17576a9142236ea542963ca5022db4332cd63aa2ed895af6888ac68",
"hex" : "4730440220456e9d366d89034c7321a900f17e60506cb9e6fb3c280587301609fda6af658502206d785719bc42de81ce05ac4b461fc9d4aab5286d4ec3ef8d0589a
b3ed1076d7501210334ae38e2f6331bfc4832893edd540377bcfc08b1a63730339b91cf8a6e0b6636067365637265744c6176a8202bb80d537b1da3e38bd30361aa855686bde0eacd7162fef6a25
fe97bf527a25b87637576a91439f079037b44caa047b19f66f9446ad29ca1835888ac6704d0dea656b17576a9142236ea542963ca5022db4332cd63aa2ed895af6888ac68"
},
"sequence" : 0
}
],
"vout" : [
{
"value" : 25.00000000,
"n" : 0,
"scriptPubKey" : {
"asm" : "OP_DUP OP_HASH160 39f079037b44caa047b19f66f9446ad29ca18358 OP_EQUALVERIFY OP_CHECKSIG",
"hex" : "76a91439f079037b44caa047b19f66f9446ad29ca1835888ac",
"reqSigs" : 1,
"type" : "pubkeyhash",
"addresses" : [
"mkoJtKoxHmdL8aXJvPudmUgZKC1xXHb9KT"
]
}
}
]
}
Now copy and paste the revealed secret:
HEX_SCRT=736563726574
[
{
"txid" : "e6af2d2c7e6cda9ea14c166a57c83112376a39b24524b5d2b1e607d740663b71",
"vout" : 0,
"address" : "2N1dPcqdkNyfNqysHDqWRq8hqSs6sT91LTP",
"account" : "user1 (user2's p2sh)",
"scriptPubKey" : "a9145bf232454e73c9cafa022f52d819bbf59c63df1087",
"amount" : 25.00000000,
"confirmations" : 9,
"spendable" : false
}
]
Now copy and paste the P2SH txid and vout:
TXID=e6af2d2c7e6cda9ea14c166a57c83112376a39b24524b5d2b1e607d740663b71
VOUT=0
Now click the Secret Checked button and paste the Secret Reveal Script:
SCRIPT=76a8202bb80d537b1da3e38bd30361aa855686bde0eacd7162fef6a25fe97bf527a25b87637576a91407f8009f5b6b12a5ae10e0ae539ea06ce232cfbf88ac67047387a756b17576a9148
e6eac4b9e5944a76f2305a736ed2a7d65742f7688ac68
0100000001713b6640d707e6b1d2b52445b2396a371231c8576a164ca19eda6c7e2c2dafe600000000d4473044022027523c5d0aaf22798d0503c67c073bf4a78522d88d8128720091289845ac0f
1d022078d69e74bea88f7d727a4a04650179136ca24872477f052f58d17f825ce1b0ad01210220d666741f2e8be672556ca8f0b7a7352516422c7b7b3f0681d39adf4cabd953067365637265744c
6176a8202bb80d537b1da3e38bd30361aa855686bde0eacd7162fef6a25fe97bf527a25b87637576a91407f8009f5b6b12a5ae10e0ae539ea06ce232cfbf88ac67047387a756b17576a9148e6eac
4b9e5944a76f2305a736ed2a7d65742f7688ac68000000000100f90295000000001976a91407f8009f5b6b12a5ae10e0ae539ea06ce232cfbf88ac00000000
Now "user1" will redeem LHS from the "user2" P2SH address tx.
Balance of LHS for "user1" is:
25.00000000
So I've built a decentralised exchange but I am getting the feeling that I have probably wasted my time doing so (am glad it hasn't taken me more than a couple of weeks). Does anyone really think that this kind of idea is going to work? |
|
|
|
|
Is Peter R the one who constantly posts "diagrams" rather than "words"?
If so then for sure he is not a very genuine person - as diagrams are generally always used to convince stupid people when you don't have the words to convince those that are not.
|
|
|
|
The CIYAM Trade package is nearly finished - in order to test it I created an application with the Trade package and used a CIYAM script to act as the wallet (I plan to add the functionality to the CIYAM's Wallet package next). Although when the Wallet package is used the UI will be improved there are still a number of steps that involve copying and pasting information - so here is what it looks like currently from the console's perspective (the Trade application UI is described so is not illustrated as you can assume it). Generating a spendable amount of RHS for "user1"...
Generating a spendable amount of LHS for "user2"...
Login as "user1" and create a Trading Pair (with Maximum Amount as at least 25) and then Logout.
Now login as "user2" and create a tx from the offer in the All Open Offers list with the following details:
Sending Amount: 25
Refund Address: mtW4pzRHXwNwkHa2mdy2EokKy5GZ4aMWtu
Receiving Address: mkoJtKoxHmdL8aXJvPudmUgZKC1xXHb9KT
Secret Hash: 2bb80d537b1da3e38bd30361aa855686bde0eacd7162fef6a25fe97bf527a25b
Now login as "user1" and edit the Trade Transaction in the My Trade Transactions list with the following:
Refund Address: mids4AKKn42KmcJTvaynUzmnhWnmfgwRMw
Receiving Address: mgF67ucKz7CddjuJwDvDUgC5HiJBRDGNBx
Now login as "user2" and from the tx click on the Waiting tx and copy and paste the Sending Address:
USER2_P2SH=2N1dPcqdkNyfNqysHDqWRq8hqSs6sT91LTP
Now "user2" will send LHS to their P2SH address.
Now login as "user1" and from the tx click on the Waiting tx and copy and paste the Sending Address:
USER1_P2SH=2NFtwQWeiQzMgeidPCrZZhATv6ULXqA8WaB
Now "user1" will send RHS to their P2SH address...
[
{
"involvesWatchonly" : true,
"account" : "user2 (user1's p2sh)",
"address" : "2NFtwQWeiQzMgeidPCrZZhATv6ULXqA8WaB",
"category" : "receive",
"amount" : 25.00000000,
"vout" : 1,
"confirmations" : 4,
"blockhash" : "55647bfcc1ea60124e3e358a046a1e6494babb666d656aec3a9ad7ea3b179e71",
"blockindex" : 1,
"blocktime" : 1453733457,
"txid" : "1b0effc3dbb318d988c5f8f3525c1e79fec7f327aebbc2028274361139042870",
"walletconflicts" : [
],
"time" : 1453733457,
"timereceived" : 1453733475
}
]
Now enter the following from the transaction information above:
TXID=1b0effc3dbb318d988c5f8f3525c1e79fec7f327aebbc2028274361139042870
VOUT=1
Now login as "user2" and from the tx click the Receive Checked button and paste the Secret Reveal Script:
SCRIPT=76a8202bb80d537b1da3e38bd30361aa855686bde0eacd7162fef6a25fe97bf527a25b87637576a91439f079037b44caa047b19f66f9446ad29ca1835888ac6704d0dea656b17576a9142
236ea542963ca5022db4332cd63aa2ed895af6888ac68
0100000001702804391136748202c2bbae27f3c7fe791e5c52f3f8c588d918b3dbc3ff0e1b01000000d44730440220456e9d366d89034c7321a900f17e60506cb9e6fb3c280587301609fda6af65
8502206d785719bc42de81ce05ac4b461fc9d4aab5286d4ec3ef8d0589ab3ed1076d7501210334ae38e2f6331bfc4832893edd540377bcfc08b1a63730339b91cf8a6e0b6636067365637265744c
6176a8202bb80d537b1da3e38bd30361aa855686bde0eacd7162fef6a25fe97bf527a25b87637576a91439f079037b44caa047b19f66f9446ad29ca1835888ac6704d0dea656b17576a9142236ea
542963ca5022db4332cd63aa2ed895af6888ac68000000000100f90295000000001976a91439f079037b44caa047b19f66f9446ad29ca1835888ac00000000
Now "user2" will redeem RHS from the "user1" P2SH address tx (exposing their secret).
Balance of RHS for "user2" is:
25.00000000
Now login as "user1" and from the tx click the Receive Checked button and paste the new Check Address:
ADDR=mkoJtKoxHmdL8aXJvPudmUgZKC1xXHb9KT
[
{
"involvesWatchonly" : true,
"account" : "user1 (user2's reveal)",
"address" : "mkoJtKoxHmdL8aXJvPudmUgZKC1xXHb9KT",
"category" : "receive",
"amount" : 25.00000000,
"vout" : 0,
"confirmations" : 1,
"blockhash" : "5ea97dcb1e76ca90ef0b71aae2208488df5d8344248be2713fbb8f1bae8a1667",
"blockindex" : 1,
"blocktime" : 1453733502,
"txid" : "d374d12b0cee799e7d3b233332b87ae41f18ffae9c1a5dc49f7436df4f216fcf",
"walletconflicts" : [
],
"time" : 1453733502,
"timereceived" : 1453733536
}
]
Now copy and paste the secret reveal txid:
TXID=d374d12b0cee799e7d3b233332b87ae41f18ffae9c1a5dc49f7436df4f216fcf
{
"txid" : "d374d12b0cee799e7d3b233332b87ae41f18ffae9c1a5dc49f7436df4f216fcf",
"version" : 1,
"locktime" : 0,
"vin" : [
{
"txid" : "1b0effc3dbb318d988c5f8f3525c1e79fec7f327aebbc2028274361139042870",
"vout" : 1,
"scriptSig" : {
"asm" : "30440220456e9d366d89034c7321a900f17e60506cb9e6fb3c280587301609fda6af658502206d785719bc42de81ce05ac4b461fc9d4aab5286d4ec3ef8d0589ab3
ed1076d7501 0334ae38e2f6331bfc4832893edd540377bcfc08b1a63730339b91cf8a6e0b6636 736563726574 76a8202bb80d537b1da3e38bd30361aa855686bde0eacd7162fef6a25fe97bf5
27a25b87637576a91439f079037b44caa047b19f66f9446ad29ca1835888ac6704d0dea656b17576a9142236ea542963ca5022db4332cd63aa2ed895af6888ac68",
"hex" : "4730440220456e9d366d89034c7321a900f17e60506cb9e6fb3c280587301609fda6af658502206d785719bc42de81ce05ac4b461fc9d4aab5286d4ec3ef8d0589a
b3ed1076d7501210334ae38e2f6331bfc4832893edd540377bcfc08b1a63730339b91cf8a6e0b6636067365637265744c6176a8202bb80d537b1da3e38bd30361aa855686bde0eacd7162fef6a25
fe97bf527a25b87637576a91439f079037b44caa047b19f66f9446ad29ca1835888ac6704d0dea656b17576a9142236ea542963ca5022db4332cd63aa2ed895af6888ac68"
},
"sequence" : 0
}
],
"vout" : [
{
"value" : 25.00000000,
"n" : 0,
"scriptPubKey" : {
"asm" : "OP_DUP OP_HASH160 39f079037b44caa047b19f66f9446ad29ca18358 OP_EQUALVERIFY OP_CHECKSIG",
"hex" : "76a91439f079037b44caa047b19f66f9446ad29ca1835888ac",
"reqSigs" : 1,
"type" : "pubkeyhash",
"addresses" : [
"mkoJtKoxHmdL8aXJvPudmUgZKC1xXHb9KT"
]
}
}
]
}
Now copy and paste the revealed secret:
HEX_SCRT=736563726574
[
{
"txid" : "e6af2d2c7e6cda9ea14c166a57c83112376a39b24524b5d2b1e607d740663b71",
"vout" : 0,
"address" : "2N1dPcqdkNyfNqysHDqWRq8hqSs6sT91LTP",
"account" : "user1 (user2's p2sh)",
"scriptPubKey" : "a9145bf232454e73c9cafa022f52d819bbf59c63df1087",
"amount" : 25.00000000,
"confirmations" : 9,
"spendable" : false
}
]
Now copy and paste the P2SH txid and vout:
TXID=e6af2d2c7e6cda9ea14c166a57c83112376a39b24524b5d2b1e607d740663b71
VOUT=0
Now click the Secret Checked button and paste the Secret Reveal Script:
SCRIPT=76a8202bb80d537b1da3e38bd30361aa855686bde0eacd7162fef6a25fe97bf527a25b87637576a91407f8009f5b6b12a5ae10e0ae539ea06ce232cfbf88ac67047387a756b17576a9148
e6eac4b9e5944a76f2305a736ed2a7d65742f7688ac68
0100000001713b6640d707e6b1d2b52445b2396a371231c8576a164ca19eda6c7e2c2dafe600000000d4473044022027523c5d0aaf22798d0503c67c073bf4a78522d88d8128720091289845ac0f
1d022078d69e74bea88f7d727a4a04650179136ca24872477f052f58d17f825ce1b0ad01210220d666741f2e8be672556ca8f0b7a7352516422c7b7b3f0681d39adf4cabd953067365637265744c
6176a8202bb80d537b1da3e38bd30361aa855686bde0eacd7162fef6a25fe97bf527a25b87637576a91407f8009f5b6b12a5ae10e0ae539ea06ce232cfbf88ac67047387a756b17576a9148e6eac
4b9e5944a76f2305a736ed2a7d65742f7688ac68000000000100f90295000000001976a91407f8009f5b6b12a5ae10e0ae539ea06ce232cfbf88ac00000000
Now "user1" will redeem LHS from the "user2" P2SH address tx.
Balance of LHS for "user1" is:
25.00000000
Clearly with the right stuff added into the Wallet package the need for dumping raw txs will disappear so it will be much cleaner but there is no real way of getting around the copying and pasting of pieces of information. For those that use Qora or Burst the AT implementation will actually be much nicer. |
|
|
|
They would rather 'die' than admit to being wrong so everything is futile. I do not want to waste any more time on such individuals even though I've really tried helping them.
I feel for you - unfortunately these people are not genuine as they are not interested in actually learning anything but instead posting incorrect information and just telling everyone else that they are right (it is also possible that they are being paid to post nonsense by those with vested interests). This is why you don't have software developed by consensus.  Luckily I think that no-one actually gives a flying fuck about what is posted by such people in this forum (already hardly any technical people bother using this forum now so I doubt that these posts are having the slightest bit of influence with those that are actually doing the development work and I would very much doubt any respectable investment companies would spend their time reading the garbage posted here either). |
|
|
|
|
Show Posts
