Pages:
Author

Topic: [ANN] OCTO - Resurrect 888 - New Counterparty Asset - page 25. (Read 37854 times)

member
Activity: 67
Merit: 10
It'd be interesting to know who that single 6.9 mill burn was

I poked about the block chain and the 7 million-er is one of us (the community not the council) if that makes you feel better :-) I wont out him, as it's up to him but with a little investigation it's quite easy to ID.

We've managed to BURN almost half of the 888 in existence :-)
full member
Activity: 208
Merit: 100
We're in the known list. woop woop. Been a long time since anything Octo related (hell crypto tbh) was fun.

So in terms of octo.party, I was having a look at some options. Personally I'm only really familiar with joomla, and have been browsing some templates to get ideas, this one here Megazine Template strikes me as a really good design. It's bold, not cluttered, and I don't think it would take too much to bang it into shape for our needs, if we are to go with the plan of using it to promote services/endeavours/etc.
legendary
Activity: 2702
Merit: 1030
Yes I am a pirate, 300 years too late!
It'd be interesting to know who that single 6.9 mill burn was

I don't know but I wish it was me:)  Thanks to the Octoparty team for making the burn process so smooth and straightforward great work!

Wasn't me either.  I had a tenth of that and I thought I was doing good!!!  Cheesy
member
Activity: 97
Merit: 10
It'd be interesting to know who that single 6.9 mill burn was

I don't know but I wish it was me:)  Thanks to the Octoparty team for making the burn process so smooth and straightforward great work!
legendary
Activity: 2702
Merit: 1030
Yes I am a pirate, 300 years too late!
I'm the 1st 2 unknowns, E-Mail sent
hero member
Activity: 742
Merit: 500
Ok, so after going through all addresses on the burn address and comparing them with the addresses filled out in the form, there seems to be no discrepancies on duplicate entries. I have been able to verify a vast majority of addresses for the burn. Now that it is late neough, the burn is over and the last block height for the burn is officially the transaction from height 316137 on the 888 chain. Here are the following TX's that i was not able to verify identities to (they had multiple inputs and i tried tracing them but could not):


  • 1b1e7735832d0544828c123bee383534f0fee9f75a15192fcc870fc94d333fe7
  • 7a0846e552f44e960e53e20137d6163d35db41352a8a35536f772eee8f4a4f13
  • ea9e891c3e5b987bab1e48057914024ebf3965b2951b351d32af8f97f4ed015c
  • d837df9cba28b8fbf2c67eb8e2b83458c212b28d1c80f7d7632d3d4672050ad4
  • 6a7d668448fcbf5a9ce8eeb5777730748855f24117ade02abb3e3856a59a1eb2
  • 0c2f72af8c85e3f1b67a81fa7f2a568d12fd71520c91cd762e85fb7063c3a850
  • 0593e6a25d749dcd6236c7a42a57c45f85825e11ee7bed968e0b9f0378f273e1
  • 91c979f61c200e5a2271f4cb9f41ae236cfae3637618060e85118453fc32527f
  • aa74c9d74da31bc10d2a199446bfc5be3cd7b3a4f14f47edfa267001b201aa74
  • 7c06648efad5fc0877e214a2efc9903664905cdd4be42ad5f653d0f8e5d6501a
  • e8e7fd0035a3739faa13006eee7c1193649b4a924ddd18fb28cd3a26d6c3800f
  • 225fa66a0ab6f22ae4ee6c0a78dc134368aee2b7a1776ad556a2a3e5425aca01
  • 3494ca5df7ec078940797302e2d0e7e1ee0fdb7b1fd60e332cad8826bff4e6bc
  • 0ef11c5721c651eb547675752883623219e8fe01b1c29b095b6ea55814e288b8
  • f1d23bc25528268ac160d9132296352d1133606798badd5800f409ce139518bf
  • 4817eed9d3dcd011ebb0a418b955b4aeead6dce8d41edeb7f56e9c071824ba4e


Here is the complete list of address plus amount to be paid, if you do not see your totals here that means you are in the above TXs and you must contact me [email protected] within 2 days or they will be disregarded:


  • 8Squidj3BzP9EYuMdy6kmsoeR8k684tRCX   1KwQxF4ZNZRosTLNNqFaH9zWjTkNEJbR7Q   0.65326356
  • 8LYf6Vfp4YkJK11mcJ2z5v49o4LvG7tAA8   1ADHMo6KGgJZRxrPUYUUVGFYeZ2noAfDRQ   2
  • 8Squidj3BzP9EYuMdy6kmsoeR8k684tRCX   1KwQxF4ZNZRosTLNNqFaH9zWjTkNEJbR7Q   1200000
  • 8LYf6Vfp4YkJK11mcJ2z5v49o4LvG7tAA8   1ADHMo6KGgJZRxrPUYUUVGFYeZ2noAfDRQ   189166.2363
  • 8SzWV6AD21xQgNGvk2283fck5jucsKC36X   1PU5WZCb6Tij4R7HD4EYiyqJAZvfp836Dj   50000
  • 8SzWV6AD21xQgNGvk2283fck5jucsKC36X   1PU5WZCb6Tij4R7HD4EYiyqJAZvfp836Dj   50000
  • 8SzWV6AD21xQgNGvk2283fck5jucsKC36X   1PU5WZCb6Tij4R7HD4EYiyqJAZvfp836Dj   50000
  • 8SzWV6AD21xQgNGvk2283fck5jucsKC36X   1PU5WZCb6Tij4R7HD4EYiyqJAZvfp836Dj   50000
  • 8SzWV6AD21xQgNGvk2283fck5jucsKC36X   1PU5WZCb6Tij4R7HD4EYiyqJAZvfp836Dj   50000
  • 8SzWV6AD21xQgNGvk2283fck5jucsKC36X   1PU5WZCb6Tij4R7HD4EYiyqJAZvfp836Dj   50000
  • 8SzWV6AD21xQgNGvk2283fck5jucsKC36X   1PU5WZCb6Tij4R7HD4EYiyqJAZvfp836Dj   50000
  • 8SzWV6AD21xQgNGvk2283fck5jucsKC36X   1PU5WZCb6Tij4R7HD4EYiyqJAZvfp836Dj   50000
  • 8SzWV6AD21xQgNGvk2283fck5jucsKC36X   1PU5WZCb6Tij4R7HD4EYiyqJAZvfp836Dj   50000
  • 8SzWV6AD21xQgNGvk2283fck5jucsKC36X   1PU5WZCb6Tij4R7HD4EYiyqJAZvfp836Dj   5700
  • 8LYMAZgeCnw3GXDikk9ucXezHQzzYVgFho   12exVAGkv8XjuEv8g5PCirJM749311wo6r   7242
  • 8XasjYTjGXx7HCigvsQbJQDTuGPbYAAkcm   1LKdNrJbEDQPcQmcwdFLiEkzaQLKXUqjQM   11784
  • 8UZrfaWu5FgAeKXpQpxPGKhZkeK2tTpzDX   18JvkeYqSZfPkdj5yGyb3zb2eEexcHaDpx   8502.329254
  • 8Y4KeR2SMVVA6xhZPhWCcgcioqH3PLREXN   1PkfomkLBuLhYtDgrwgboXfpJotDA8gkjT   114.5573137
  • 8aCkrmcZewHm83edT8RU97qe8UFqRbdXmQ   1BYnoxuP4a35c3MCtmtpBHkqLYEVm3hCcp   44075.97884
  • 8LYf6Vfp4YkJK11mcJ2z5v49o4LvG7tAA8   1ADHMo6KGgJZRxrPUYUUVGFYeZ2noAfDRQ   350000.43
  • 8Z53PmseZjw9v8EfwyAeYRfTc7xk8ufckP   161kRh24UQpSWx9hLSneZpedRtDPYr823L   579470.2593
  • 8TFCHvTMuK2ihtmGSEMk7qsNNwAFCferWV   12uWfvwNhPfWxTxERtGURm9XxvdQ4U3X56   113721
  • 8Rbs4cwJoedJh46JXNPCgMBg5HDQsy5nL7   1MtzLp6ZgxFfTYEgKqwZBrRgv7oe3WstHU   165026.4565
  • 8QxLvV7DCDce2bPg31wm3rr3KxBaYT4t3n   1A8VAJE465cJyP3Lhx1ndQQ7FzBqdYB8GL.   86700
  • 8d1knHZ7geaqaD734yoPXscXfydPGGzDta   12XmyDrmLaSET6fmgAUk5NDeZrL5BN9Qcc   76141
  • 8LN1471LRVoqd3JR9g9Q3n6zE8VrHz2fbn   1JXSpqC76izgCvhVvpbQmizM6fYVSjEyBd   109429
  • 8HruqzfQHFFViPSxobCSsCRsvV8LdcA8uR   1FLyThjyJtw3cTiHNGdk1Ks7wjYqmwDPYp   80000
  • 8PT6tPktZHYdakrXXfNYGDF2ZAnv87BZxJ   191D7fHD38MdGYfpn7aDApDr3js3TxD5Zm   21108.5975
  • 8SFCycPqxBa9M1VaaWa8NYdfZi19rG5b54   15BfDCHgXbokh7fNq5d8GAHLHW6zXyjPa3   1579135
  • 8XCKM8Mbdh8DB4BmeMR9Rw5XaRetEeDNrZ   1Fh3vLqZxvv7j1YDtnacqiJkvdWbCHGPCi   1385
  • 8XCKM8Mbdh8DB4BmeMR9Rw5XaRetEeDNrZ   1Fh3vLqZxvv7j1YDtnacqiJkvdWbCHGPCi   5000
  • 8XCKM8Mbdh8DB4BmeMR9Rw5XaRetEeDNrZ   1Fh3vLqZxvv7j1YDtnacqiJkvdWbCHGPCi   35001
  • 8PkZ22Dt1bwGdm1TicfQdtYBmtnQ3vBfYF   1BkaQxZvBqhWVztZ7XUHaNE1QyWHR889Ly   750672
  • 8GRh9ywgoPhSNMca4VrtX4UkCERRb62vVU   1NGw5isEd7hAfH1tNiFX5F2CWKz7D7jTKo   1157109.865
  • 8TcNUqrARkX2yCwwuGHnpBnPUSHb9T7wK8   1GSt5RtCvmiUZz1ebkSE3QxTFLorfXP6Bm.   20511.77702
  • 8WTSc5fSMWytCkjd7zdwMX4JyxoJTDRnmJ   1HK1GV1tyB4ySJjgxGvxnhC8v3FKsAhpgi   7255
  • 8ZeA7ZCCTuBTFXAJ7HnnP5bXdAhpTYCfaX   15v7thTvTBboKhMAwqBWMBkZqbrSLj1kcm   1396066
  • 8Ggm8cU8zGaBGY7uEUCALD8TFZ7ehDLaMX   13HWhNZS4gZ38g2LiBcYxHuxRHseaWWroW   200209
  • 8dXEFWts7JiFGPd5jCy3RHcy3G6rNikGCx   1A4wpR34AWCiTb3Go63zjuVGRb6E8ow3jZ   999
  • 8dXEFWts7JiFGPd5jCy3RHcy3G6rNikGCx   1A4wpR34AWCiTb3Go63zjuVGRb6E8ow3jZ   184400
  • 8SMr6HJ8J19Pwbfka6FUya8kMNTAczV6WZ   16Xhu2F4gM7XgMcSXNaWhxkz7YmNcZxKzC   6026.522138
  • 8a3TXBXArfLsagX11cezWEEsqLDoRFhQt7   1Q1FfD46MFosv3k7T1C5wAxUYEZ3HBWP4q   1.69998647
  • 8W5ZvSTb3QcXqfiq3JzVpRxu4o3DWqtQ8v   17KAHzZqjg9wmBhGahzSpGE2wS7sZ45BAQ   215
  • 8W5ZvSTb3QcXqfiq3JzVpRxu4o3DWqtQ8v   17KAHzZqjg9wmBhGahzSpGE2wS7sZ45BAQ   50000
  • 8W5ZvSTb3QcXqfiq3JzVpRxu4o3DWqtQ8v   17KAHzZqjg9wmBhGahzSpGE2wS7sZ45BAQ   50000
  • 8W5ZvSTb3QcXqfiq3JzVpRxu4o3DWqtQ8v   17KAHzZqjg9wmBhGahzSpGE2wS7sZ45BAQ   50000
  • 8W5ZvSTb3QcXqfiq3JzVpRxu4o3DWqtQ8v   17KAHzZqjg9wmBhGahzSpGE2wS7sZ45BAQ   42323.27517
  • 8W5ZvSTb3QcXqfiq3JzVpRxu4o3DWqtQ8v   17KAHzZqjg9wmBhGahzSpGE2wS7sZ45BAQ   45106.94137
  • 8W5ZvSTb3QcXqfiq3JzVpRxu4o3DWqtQ8v   17KAHzZqjg9wmBhGahzSpGE2wS7sZ45BAQ   47258.86196
  • 8W5ZvSTb3QcXqfiq3JzVpRxu4o3DWqtQ8v   17KAHzZqjg9wmBhGahzSpGE2wS7sZ45BAQ   45251.05188
  • 8W5ZvSTb3QcXqfiq3JzVpRxu4o3DWqtQ8v   17KAHzZqjg9wmBhGahzSpGE2wS7sZ45BAQ   25060.65842
  • 8XWXEP3rhXdrrx4tVvjPuntwypDRQrf8J6   1KSvQCYZWp9GoUdprEdA8E6jLW45BVcZqW   6914576.472
  • 8Squidj3BzP9EYuMdy6kmsoeR8k684tRCX   1KwQxF4ZNZRosTLNNqFaH9zWjTkNEJbR7Q   64013
  • 8XmBJqGesQ1aXDAjr1bVDPTh66MPE9dHix   1F2bnyqqW2yKtSbQ3qkNAagnjGiAM5VC8g   259390
  • 8KVxyyWTyiFcqBuNjysVAoNRAqP6Rtjn9o   1PBwTiXhr1M3dqDyH1WjL5XJGnwXRVKZgd   500329.361
  • 8KVxyyWTyiFcqBuNjysVAoNRAqP6Rtjn9o   1PBwTiXhr1M3dqDyH1WjL5XJGnwXRVKZgd   509998.5398
  • 8KVxyyWTyiFcqBuNjysVAoNRAqP6Rtjn9o   1PBwTiXhr1M3dqDyH1WjL5XJGnwXRVKZgd   99997.14
  • 8SdYppydDfAQWDbwdy8Ndyz9TqDYNpJiW5   1HGiNEiz2XJkMtEVyCgqorA7NdAT9TjAYn   1005029.378
  • 8SdYppydDfAQWDbwdy8Ndyz9TqDYNpJiW5   1HGiNEiz2XJkMtEVyCgqorA7NdAT9TjAYn   6098.3198
  • 8SdYppydDfAQWDbwdy8Ndyz9TqDYNpJiW5   1HGiNEiz2XJkMtEVyCgqorA7NdAT9TjAYn   11563.693
  • 8JvB8mZu74sa8YdHxysDSXbFXpteWcnPdk   13f33D5Km4har8V9xiSv1ZFgDddBq6bwGV   49999
  • 8JvB8mZu74sa8YdHxysDSXbFXpteWcnPdk   13f33D5Km4har8V9xiSv1ZFgDddBq6bwGV   49998
  • 8QFWSHn6REu6gcCKw8NnD6rryEQcY72KPY   1H8BcPq5MNGHYcYXTkG4Q2VR2WhbPnmw2c   328934
  • 8ZvYz8GmjZZpQgFKcEcGcNgDn8eKF3n6RJ   1JpeoYpzJErdjmCVm4qJQmCkLYHSV9ZHVF   9999
  • 8ZvYz8GmjZZpQgFKcEcGcNgDn8eKF3n6RJ   1JpeoYpzJErdjmCVm4qJQmCkLYHSV9ZHVF   9999
  • 8ZvYz8GmjZZpQgFKcEcGcNgDn8eKF3n6RJ   1JpeoYpzJErdjmCVm4qJQmCkLYHSV9ZHVF   999
  • 8ZvYz8GmjZZpQgFKcEcGcNgDn8eKF3n6RJ   1JpeoYpzJErdjmCVm4qJQmCkLYHSV9ZHVF   9999
  • 8ZvYz8GmjZZpQgFKcEcGcNgDn8eKF3n6RJ   1JpeoYpzJErdjmCVm4qJQmCkLYHSV9ZHVF   9999
  • 8ZvYz8GmjZZpQgFKcEcGcNgDn8eKF3n6RJ   1JpeoYpzJErdjmCVm4qJQmCkLYHSV9ZHVF   9999


You can find the complete breakdown with TX and timestamps on this document https://docs.google.com/spreadsheets/d/14ZFfxgmRAeukUN8vcPHIaxAdue_-eGzc9dD5yhDL-Vc/pubhtml at the provided link


here is the original form list as well https://docs.google.com/spreadsheets/d/13nfukjfGvfwwI6Y2dUY13eVZLF6NmslkvXtx7GczO-g/pubhtml
newbie
Activity: 42
Merit: 0
hashbrown9000, sorry I fell asleep Smiley

sr. member
Activity: 427
Merit: 250
It'd be interesting to know who that single 6.9 mill burn was
hero member
Activity: 742
Merit: 500
Thank you Cheesy I am verifying all of the forms right now to make sure there was not any duplicate entries in the google doc. If there was (for example, someone sees a high 888 address and says they own it, hoping that someone will burn it so they can receive the new OCTO) then we will need to do digital signing. So far no foul play.

I will update as i go through all of the addresses Cheesy
hero member
Activity: 532
Merit: 500
blockscan.com/assetInfo/OCTO  OCTO is now locked asset at 88.8 million tokens
sr. member
Activity: 364
Merit: 250
Damn, all I can say is that you guys seriously ROCK!! Thanks doesn't even cut it, but thanks for all of your hard work man! Truly, truly, appreciated by me and others I am sure. Excellent!
hero member
Activity: 742
Merit: 500
tx id's have always worked for me when requesting coins during an ICO, or otherwise proving I've sent something to someone. It's on the blockchain so you really can't fake it.
True, thats what we are doing right now, going through the burn address and recording the tx ids for future verification, but we need someone to still send the 888 to the burn address for additional verification
sr. member
Activity: 427
Merit: 250
tx id's have always worked for me when requesting coins during an ICO, or otherwise proving I've sent something to someone. It's on the blockchain so you really can't fake it.
hero member
Activity: 742
Merit: 500
We have to do everything in our power to avoid having to take a screen shoot, or someones word for a burn. The whole point of the burn address is to have something provable that folks actually indeed did partake in the burn. Screen shoots can be altered via photo shop and other trust issues can come into place.

Not saying that any of you would, but you do have an old dev team that is probably watching this burn very closely and something like this would give an opportunity to exploit some issues. As long as Kris is up for it, i think anyone on here looking to do the burn throughout the night would be ok to work with me even past the deadline. I know how deadlines go, usually a lot of people wait until the end, espeially if you have kept mining before the burn. What are your thoughts kris? Can everyone work through the night with me, and once tthis night is over, consider all other requests for a burn void?

I agree. As I said, the screen shots are a precaution to prove what you have. But think about it. IF the burn address shows 18 million or so and we issue 22 million, then it's a trust factor and not proof of the blockchain factor. The integrity of the burn is at risk doing it this way. I'm ok with an extension per se. And yes that would be a better option. But remember this, it's not an extension per se for you guys to add to your total coin coint. We have to think about the size of the burn being honestly what the deadline would have allowed.
Fair enough Cheesy
hero member
Activity: 532
Merit: 500
We have to do everything in our power to avoid having to take a screen shoot, or someones word for a burn. The whole point of the burn address is to have something provable that folks actually indeed did partake in the burn. Screen shoots can be altered via photo shop and other trust issues can come into place.

Not saying that any of you would, but you do have an old dev team that is probably watching this burn very closely and something like this would give an opportunity to exploit some issues. As long as Kris is up for it, i think anyone on here looking to do the burn throughout the night would be ok to work with me even past the deadline. I know how deadlines go, usually a lot of people wait until the end, espeially if you have kept mining before the burn. What are your thoughts kris? Can everyone work through the night with me, and once tthis night is over, consider all other requests for a burn void?

I agree. As I said, the screen shots are a precaution to prove what you have. But think about it. IF the burn address shows 18 million or so and we issue 22 million, then it's a trust factor and not proof of the blockchain factor. The integrity of the burn is at risk doing it this way. I'm ok with an extension per se. And yes that would be a better option. But remember this, it's not an extension per se for you guys to add to your total coin coint. We have to think about the size of the burn being honestly what the deadline would have allowed.
hero member
Activity: 742
Merit: 500
We have to do everything in our power to avoid having to take a screen shoot, or someones word for a burn. The whole point of the burn address is to have something provable that folks actually indeed did partake in the burn. Screen shoots can be altered via photo shop and other trust issues can come into place.

Not saying that any of you would, but you do have an old dev team that is probably watching this burn very closely and something like this would give an opportunity to exploit some issues. As long as Kris is up for it, i think anyone on here looking to do the burn throughout the night would be ok to work with me even past the deadline. I know how deadlines go, usually a lot of people wait until the end, espeially if you have kept mining before the burn. What are your thoughts kris? Can everyone work through the night with me, and once tthis night is over, consider all other requests for a burn void?
member
Activity: 67
Merit: 10
Well 2 hours in and I've got them into 1 address and in only 6 inputs. Managed to send the whole shabang to WartyWarlock, he's in the process of taking the burn steps so I think we should be ok. In case he has any issues the transaction ID proving our quantity of coins (me sending them to him) is dc22e3dcd41db8944363330aa3aaf79c8f128d2e8dca16b4ae56b46c398d8134 showing 324,000 ish coins. Hopefully he'll have it sorted asap, after all the deadline is a couple of hours to go and he's at work in 7 hours...

Thanks for the consideration though.

For anyone else having the small coins limit, I was changing stuff in the 'input' section of the send screen (I'll be honest I'm not entirely sure what I was doing as it's all kinda un-labled (such as the tick box and text box...?) but it worked...) My goal was to reduct the (vast) number of inputs in the wallet a la GWcalverts suggestion from a couple of pages ago.

EDIT: Hazaar, he beat me to it...
hero member
Activity: 532
Merit: 500
BC octo now sent to burn address, time for sleep (2AM UK time) 328k

sweet, so your transaction went through with the total amount? good, maybe it was just a network hiccup.
full member
Activity: 208
Merit: 100
BC octo now sent to burn address, time for sleep (2AM UK time) 328k
hero member
Activity: 532
Merit: 500
guys we may have a solution instead of sending in a ton of 999 transactions.

who knows what is causing the issue. Robert is looking at the issue right now.

i'd suggest taking screen shots of your octocoin wallet balances and addresses. we may have to just have you email those into us with proof of the amounts you were attempting to burn and your counterwallet address.

keep in mind. this is not an extension to keep mining after midnight and have more Octocoin to burn. we need to keep some honesty and the midnight deadline honest.

however, in this instance where miners were keeping us able to burn, it would not be fair if you guys couldn't burn. i totally thank you for keeping the blockchain going and want you to have the oppurtunity to receive your OCTO because the miners keeping the blockchain up the last few months deserve that.

[email protected] and [email protected]

those are the addresses you will need to send your proof to if you cannot send octo transactions into the burn address or you cannot get over the 999. some of you have a large quanity of coins and that would be hundreds of transactions. who knows what that many transactions would do further to the network.

if we do this, then all emails of proof must be received before the burn deadline. this is not an extension. this is a prove what you have at your addresses and we will work with that.

if anyone has any better ideas, by all means, post them.

of course doing it this way means that we will have a total number of OCTO distributed that is a little higher than what the burn address can prove. but i'm pretty sure the posts and such document that this was happening along with the block chain that shows the 999 transactions. i know i had someone check and he could not send more than 999.
Pages:
Jump to: