Telephone Lemien [ARCHIVE] / is on Nostr

⚠️ This account is not associated with a real person. It's an archival account for mailing list messages.
🗓️ Active from 2015-04-30 to 2015-05-27
💬 Posted a total of 4 messages
📚 Participated in the following categories: Bitcoin-development
🔇 Please do not DM this user as it's used for archive purposes only.

Last Notes

2023-06-07 15:35:49

- reply

📅 Original date posted:2015-05-27
📝 Original message:Please remove me from the mailing list
2015-05-27 3:50 GMT+02:00 Mark Friedenbach <mark at friedenbach.org>:
> Sequence numbers appear to have been originally intended as a mechanism
> for transaction replacement within the context of multi-party transaction
> construction, e.g. a micropayment channel. The idea is that a participant
> can sign successive versions of a transaction, each time incrementing the
> sequence field by some amount. Relay nodes perform transaction replacement
> according to some policy rule making use of the sequence numbers, e.g.
> requiring sequence numbers in a replacement to be monotonically increasing.
>
> As it happens, this cannot be made safe in the bitcoin protocol as
> deployed today, as there is no enforcement of the rule that miners include
> the most recent transaction in their blocks. As such, any protocol relying
> on a transaction replacement policy can be defeated by miners choosing not
> to follow that policy, which they may even be incentivised to do so (if
> older transactions provide higher fee per byte, for example). Transaction
> replacement is presently disabled in Bitcoin Core.
>
> These shortcomings can be fixed in an elegant way by giving sequence
> numbers new consensus-enforced semantics as a relative lock-time: if a
> sequence number is non-final (MAX_INT), its bitwise inverse is interpreted
> as either a relative height or time delta which is added to the height or
> median time of the block containing the output being spent to form a
> per-input lock-time. The lock-time of each input constructed in this manor,
> plus the nLockTime of the transaction itself if any input is non-final must
> be satisfied for a transaction to be valid.
>
> For example, a transaction with an txin.nSequence set to 0xffffff9b [==
> ~(uint32_t)100] is prevented by consensus rule from being selected for
> inclusion in a block until the 100th block following the one including the
> parent transaction referenced by that input.
>
> In this way one may construct, for example, a bidirectional micropayment
> channel where each change of direction increments sequence numbers to make
> the transaction become valid prior to any of the previously exchanged
> transactions.
>
> This also enables the discussed relative-form of CHECKLOCKTIMEVERIFY to be
> implemented in the same way: by checking transaction data only and not
> requiring contextual information like the block height or timestamp.
>
> An example implementation of this concept, as a policy change to the
> mempool processing of Bitcoin Core is available on github:
>
> https://github.com/maaku/bitcoin/tree/sequencenumbers
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150527/ed83c67b/attachment.html>

2023-06-07 15:34:58

- reply

📅 Original date posted:2015-05-12
📝 Original message:Hello evry body,
I want to know what is the difference between a bitcoin transaction and
colored coins transaction technically.
Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150512/638501ae/attachment.html>

2023-06-07 15:34:58

- reply

📅 Original date posted:2015-05-12
📝 Original message:Thank You,
I know this, but I want to have mores details in the inputs/outputs, or in
the script of input/output and how i will proceed in the code.
Thanks for all replaying
2015-05-12 11:47 GMT+02:00 Patrick Mccorry (PGR) <
patrick.mccorry at newcastle.ac.uk>:
> There is no difference to the transaction as far as im aware – just the
> inputs / outputs have a special meaning (and should have a special order).
> So you can track 1 BTC throughout the blockchain and this 1 BTC represents
> my asset. Someone may give a more useful answer.
>
>
>
> *From:* Telephone Lemien [mailto:lemientelephone at gmail.com]
> *Sent:* 12 May 2015 10:45
> *To:* Bitcoin Dev
> *Subject:* [Bitcoin-development] Bitcoin transaction
>
>
>
> Hello evry body,
>
> I want to know what is the difference between a bitcoin transaction and
> colored coins transaction technically.
>
> Thanks
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150512/f5200cd8/attachment.html>

2023-06-07 15:32:36

- reply

📅 Original date posted:2015-04-30
📝 Original message:Hello,
I'm a beginner in Bitcoin and I want to know, what are things those allo me
to understand Bitcoin protocol and make progress in java to become a good
developper.
Please tell me how I can begin.
Best regards
2015-04-30 10:08 GMT+02:00 Jorge Timón <jtimon at jtimon.cc>:
> As Mike says it depends on your interests. But one thing that is almost
> always welcomed is improving the tests, and it is unlikely that it
> conflicts with other people's PRs (unless they're changing that part of the
> code and need to update those tests. Improving documentation is also good
> and you can do that while reading the code. Usually I just start cloning,
> compiling and changing things as I read, "if I understand this correctly,
> this change should not break the tests, if I understand this, this other
> change should break the build", etc.
> But again, is up to you.
> On Apr 16, 2015 2:34 PM, "Mike Hearn" <mike at plan99.net> wrote:
>
>> Hey Gabe,
>>
>> That's diving into the deep end for sure! :)
>>
>>> What are some current things that are lacking in Bitcoin core? Or am I
>>> better off making something else for the ecosystem?
>>>
>> That depends on your interests.
>>
>> Many of the highest priority tasks in Bitcoin Core are rather
>> complicated, unfortunately, even for people with experience. You can
>> consult the issue tracker to get a feel for it.
>>
>> Alternatively, there are lots of wallet apps out there and plenty of more
>> straightforward projects on them. However they may have less of a research
>> flavour.
>>
>>
>> ------------------------------------------------------------------------------
>> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
>> Develop your own process in accordance with the BPMN 2 standard
>> Learn Process modeling best practices with Bonita BPM through live
>> exercises
>> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-
>> event?utm_
>> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development at lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>
>>
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150430/b9fb571c/attachment.html>