Oldminer
Legendary
Offline
Activity: 1022
Merit: 1001
|
|
June 21, 2013, 12:03:26 PM |
|
The only "improvement" of Worldcoin is 60 seconds blocks...
15 actually..
|
|
|
|
jackjack
Legendary
Offline
Activity: 1176
Merit: 1280
May Bitcoin be touched by his Noodly Appendage
|
|
June 21, 2013, 12:08:48 PM |
|
The only "improvement" of Worldcoin is 60 seconds blocks...
15 actually.. So for you changing the retarget time is more "constituting doing something" than making transaction commentable? Interesting
|
Own address: 19QkqAza7BHFTuoz9N8UQkryP4E9jHo4N3 - Pywallet support: 1AQDfx22pKGgXnUZFL1e4UKos3QqvRzNh5 - Bitcointalk++ script support: 1Pxeccscj1ygseTdSV1qUqQCanp2B2NMM2 Pywallet: instructions. Encrypted wallet support, export/import keys/addresses, backup wallets, export/import CSV data from/into wallet, merge wallets, delete/import addresses and transactions, recover altcoins sent to bitcoin addresses, sign/verify messages and files with Bitcoin addresses, recover deleted wallets, etc.
|
|
|
Oldminer
Legendary
Offline
Activity: 1022
Merit: 1001
|
|
June 21, 2013, 12:14:12 PM |
|
The only "improvement" of Worldcoin is 60 seconds blocks...
15 actually.. So for you changing the retarget time is more "constituting doing something" than making transaction commentable? Interesting So, one moment your backing some coin that is clearly no different to any other alt thats been released, and the next your trying to bag some other coin like you know what your talking about, when clearly you know nothing about it (or you wouldnt be asking me). Crypto clearly isnt your forte jacky boy. Why dont you take up baseball or a craft like sewing?
|
|
|
|
jackjack
Legendary
Offline
Activity: 1176
Merit: 1280
May Bitcoin be touched by his Noodly Appendage
|
|
June 21, 2013, 12:43:37 PM |
|
The only "improvement" of Worldcoin is 60 seconds blocks...
15 actually.. So for you changing the retarget time is more "constituting doing something" than making transaction commentable? Interesting So, one moment your backing some coin that is clearly no different to any other alt thats been released, and the next your trying to bag some other coin like you know what your talking about, when clearly you know nothing about it (or you wouldnt be asking me). Crypto clearly isnt your forte jacky boy. Why dont you take up baseball or a craft like sewing? 1. I don't back this coin: I think comments for transactions is a bad idea
Isn't it enough clear? 2. I never asked you anything 3. That doesn't answer my question Do you think changing the retarget time is more "constituting doing something" than making transaction commentable? Thank you for answering instead of trying to upsetting me
|
Own address: 19QkqAza7BHFTuoz9N8UQkryP4E9jHo4N3 - Pywallet support: 1AQDfx22pKGgXnUZFL1e4UKos3QqvRzNh5 - Bitcointalk++ script support: 1Pxeccscj1ygseTdSV1qUqQCanp2B2NMM2 Pywallet: instructions. Encrypted wallet support, export/import keys/addresses, backup wallets, export/import CSV data from/into wallet, merge wallets, delete/import addresses and transactions, recover altcoins sent to bitcoin addresses, sign/verify messages and files with Bitcoin addresses, recover deleted wallets, etc.
|
|
|
frobley
|
|
June 21, 2013, 01:03:23 PM |
|
hummm, will we see a block explorer for this coin? seeing as that is the fun part...
|
|
|
|
gnode
|
|
June 21, 2013, 02:19:06 PM |
|
hummm, will we see a block explorer for this coin? seeing as that is the fun part...
I can tell you now, you will see a lot of "services rendered"
|
|
|
|
coinerd
|
|
June 21, 2013, 05:57:08 PM |
|
can someone send me some TXid with messages in them? hunting block by block gets ooold
|
|
|
|
skyangel (OP)
Sr. Member
Offline
Activity: 301
Merit: 260
FLO dev
|
|
June 21, 2013, 05:58:39 PM |
|
can someone send me some TXid with messages in them? hunting block by block gets ooold
Status: 112 confirmations, broadcast through 4 nodes Date: 2013/06/21 18:15 Transaction ID: de2824f54ccf5391bfc0c9b5a0a5e09214e4c045627a44c696bfb325f20c92ce Transaction comment: text:Go with the FLO
|
|
|
|
|
|
coinerd
|
|
June 21, 2013, 06:41:32 PM |
|
ok well, I've had one test draw here: http://lotto.coinworld.us/FLO/It seems to be running fine, what sort of ticket price/drawing interval are FLO users interested in? Also thanks frobley. Is it always the same number of characters or how do i recognize that? Sorry for the noob questions but I'm not familiar with this sort of thing.
|
|
|
|
skyangel (OP)
Sr. Member
Offline
Activity: 301
Merit: 260
FLO dev
|
|
June 21, 2013, 06:44:48 PM Last edit: June 21, 2013, 07:00:25 PM by skyangel |
|
02000000010cd18acf5f2a854e93cc88058fc59c95c7b97ed2f255900bc0829a1f813d0b7801000 0006b483045022100ec82001cca4924e0f9b857153a0e6e07bcb5d657b090b870929014a14dbe6c f602207047b247b6c6b99f985406d9df184c81ff302b01c0dea1c396df1b8d0061713f0121037e6 9a13d14797dc3d9555cc75da616edb9c1a058876183fe0171f85c7ebf2672ffffffff02c35d462a 010000001976a914e969fd5fb098999ab4df96429cf33aed4f33fe0788ac00ab904100000000197 6a914ad5de988256a98eee955c77b1e92c7ff065ebf9988ac00 0000001b746578743a476f207769746820746865203c423e464c4f3c2f423e1b (27) is the length of the message. The full message is: "text:Go with the <B>FLO</B>" In hex: 746578743a476f207769746820746865203c423e464c4f3c2f423e Also note that only those transactions that have "Tx version" = 2 have a message at the end.
|
|
|
|
skyangel (OP)
Sr. Member
Offline
Activity: 301
Merit: 260
FLO dev
|
|
June 21, 2013, 07:05:59 PM |
|
ok well, I've had one test draw here: http://lotto.coinworld.us/FLO/It seems to be running fine, what sort of ticket price/drawing interval are FLO users interested in? Also thanks frobley. Is it always the same number of characters or how do i recognize that? Sorry for the noob questions but I'm not familiar with this sort of thing. Looks nice. Got myself a few tickets
|
|
|
|
coinerd
|
|
June 21, 2013, 07:40:52 PM |
|
Also note that only those transactions that have "Tx version" = 2 have a message at the end.
ok thanks a lot, that should help. It looks like if I send it all through a hex to ascii conversion i get a bunch of gibberish then "Text: and the cleartext message. Is there a reason I shouldn't just trap for that? It seems to be the end of the hex data each time. Along with the tx version it should make things simple. Looks nice. Got myself a few tickets Thanks I'm glad you like it, I've had mixed responses to the theme. I still need to make some of those nav items images I think. If there's any feedback I can make adjustments right now it sets drawing time for approximately 6 hours.
|
|
|
|
skyangel (OP)
Sr. Member
Offline
Activity: 301
Merit: 260
FLO dev
|
|
June 21, 2013, 08:01:08 PM |
|
Also note that only those transactions that have "Tx version" = 2 have a message at the end.
ok thanks a lot, that should help. It looks like if I send it all through a hex to ascii conversion i get a bunch of gibberish then "Text: and the cleartext message. Is there a reason I shouldn't just trap for that? It seems to be the end of the hex data each time. Along with the tx version it should make things simple. The "text:" part is not guaranteed to always be there. It is only there if you send through the GUI. The best would be to parse the whole message like under the "Raw Transaction Detail" part on the web-site, but I don't know how easy it will be. A quick way might be to do like you suggested and only look for "text:" messages. The length byte will always be before that, so you can validate that you are in the right spot. Since messages are currently a maximum of 140 characters, the three bytes before the length byte should be 0. Also remember that the message could contain anything, so if you display it on a web site there might be HTML in the message. You should "clean up" the message before displaying on a web site.
|
|
|
|
coinerd
|
|
June 21, 2013, 08:20:03 PM |
|
The "text:" part is not guaranteed to always be there. It is only there if you send through the GUI. The best would be to parse the whole message like under the "Raw Transaction Detail" part on the web-site, but I don't know how easy it will be.
A quick way might be to do like you suggested and only look for "text:" messages. The length byte will always be before that, so you can validate that you are in the right spot. Since messages are currently a maximum of 140 characters, the three bytes before the length byte should be 0. Also remember that the message could contain anything, so if you display it on a web site there might be HTML in the message. You should "clean up" the message before displaying on a web site.
This is going to be a stab in the dark.. those things you're saying, I know what they mean but i have no idea how to sort out the bytes and etc... I see already that v2 tx don't always have a text. preg_split is probably the extent of my brain stretching today EDIT and maybe some htmlspecialchars heh
|
|
|
|
skyangel (OP)
Sr. Member
Offline
Activity: 301
Merit: 260
FLO dev
|
|
June 21, 2013, 08:24:51 PM |
|
This is going to be a stab in the dark..
Good luck
|
|
|
|
|
coinerd
|
|
June 21, 2013, 09:23:23 PM |
|
http://lotto.coinworld.us/FLO/bc/index.phpok you can find your messages there for now, I was able to find a few messages and it seems to work. Thank you very much skyangel for the tips. I'll be merging that with some other code and cleaning it up a little later. There's no database so it's hard to browse for random transactions but if you have a TXid it's fine. I've never released this code before so if you run into anything odd feel free to drop me a PM thanks. I'm working with MobGod to get some lottos up at http://lotto.coinworld.us/ since I wanted to check out this messaging FLO is one of the first coins added. It will have a coin and a link on the front page within the next hour or so. Compared to 6coin and 8coin this is pretty damn innovative on my chart. It would be nice to have the old bitcoin message (comment) stubs either removed, or activated for this feature. Did you save time by implementing it in parallel or do you have other ideas for expansion?
|
|
|
|
metacoin
|
|
June 21, 2013, 09:24:18 PM |
|
The "text:" part is not guaranteed to always be there. It is only there if you send through the GUI. The best would be to parse the whole message like under the "Raw Transaction Detail" part on the web-site, but I don't know how easy it will be.
A quick way might be to do like you suggested and only look for "text:" messages. The length byte will always be before that, so you can validate that you are in the right spot. Since messages are currently a maximum of 140 characters, the three bytes before the length byte should be 0. Also remember that the message could contain anything, so if you display it on a web site there might be HTML in the message. You should "clean up" the message before displaying on a web site.
This is going to be a stab in the dark.. those things you're saying, I know what they mean but i have no idea how to sort out the bytes and etc... I see already that v2 tx don't always have a text. preg_split is probably the extent of my brain stretching today EDIT and maybe some htmlspecialchars heh function hex2str($hex) { for($i=0;$i<strlen($hex);$i+=2) $str .= chr(hexdec(substr($hex,$i,2))); $str=substr($str, strpos($str, 'text:')); return $str; } Also, I sent you a PM. Please respond when you can
|
pin.org
|
|
|
|