Symfony Profiler

Query Metrics

1 Database Queries

1 Different statements

23.48 ms Query time

0 Invalid entities

0 Cache hits

0 Cache misses

0 Cache puts

Queries

Group similar statements

#▲	Time	Info
1	23.48 ms	INSERT INTO messenger_messages (body, headers, queue_name, created_at, available_at) VALUES(?, ?, ?, ?, ?) Parameters: ["{"payload":"{\"@context\":[\"https:\/\/join-lemmy.org\/context.json\",\"https:\/\/www.w3.org\/ns\/activitystreams\"],\"actor\":\"https:\/\/lemmy.world\/c\/memes\",\"to\":[\"https:\/\/www.w3.org\/ns\/activitystreams#Public\"],\"object\":{\"id\":\"https:\/\/lemmy.world\/activities\/create\/aa9176c9-28ee-4c8e-a87b-a7631823e5e1\",\"actor\":\"https:\/\/lemmy.world\/u\/Knock_Knock_Lemmy_In\",\"to\":[\"https:\/\/www.w3.org\/ns\/activitystreams#Public\"],\"object\":{\"type\":\"Note\",\"id\":\"https:\/\/lemmy.world\/comment\/16530237\",\"attributedTo\":\"https:\/\/lemmy.world\/u\/Knock_Knock_Lemmy_In\",\"to\":[\"https:\/\/www.w3.org\/ns\/activitystreams#Public\"],\"cc\":[\"https:\/\/lemmy.world\/c\/memes\",\"https:\/\/slrpnk.net\/u\/umbraroze\"],\"content\":\"<blockquote>\\n<p>What you\u2019re talking about is using technical solution to <em>mitigate<\/em> problems in the organisational level.<\/p>\\n<\/blockquote>\\n<p>No. Blockchain is for solving intraorganisational problems. I.e. How can the invoices of your suppliers be made available.<\/p>\\n<blockquote>\\n<p>There\u2019s little you can do on technical level to 100% ensure that invoice information is correct and matches what is actually happening in the real world.<\/p>\\n<\/blockquote>\\n<p>This is known as the Oracle problem.<\/p>\\n<blockquote>\\n<p>a series of interoperable systems, which is how things generally work.<\/p>\\n<\/blockquote>\\n<p>But they don\u2019t work, because one cannot confirm who entered or manipulated the data, or whether the data has been altered in a malicious manner.<\/p>\\n<blockquote>\\n<p>what do you do in cases where the supply chain is <em>deliberately<\/em> opaque? What if this information is something that companies cannot, for one reason or other, share with one another?<\/p>\\n<\/blockquote>\\n<p>This is where Zero Knowledge is used. A trusted third party \u00a9 certifies some data as correct (I.e. a birthday) then the supplier can then create a proof that all their employees are over 18 as certified by \u00a9 but the actual ages are not disclosed.<\/p>\\n<blockquote>\\n<p>But nothing stops them from accessing (and copying) the information while they have legitimate access to it!<\/p>\\n<\/blockquote>\\n<p>True with or without blockchain.<\/p>\\n<blockquote>\\n<p>it can be done without a blockchain.<\/p>\\n<\/blockquote>\\n<p>Blockchain controls access without needing to set up authentication for all users.<\/p>\\n<blockquote>\\n<p>And what do you propose happens when the blockchain just straight up isn\u2019t accessible anymore for one reason or other?<\/p>\\n<\/blockquote>\\n<p>If availability is important then you run your own node. You also choose a flavor of blockchain that has very little downtime.<\/p>\\n<blockquote>\\n<p>Nothing in blockchain specifically ensures this kind of longevity.<\/p>\\n<\/blockquote>\\n<p>Agreed, blockchain creates permanent immutability, it does not guarantee permanent availability.<\/p>\\n<blockquote>\\n<p>Nothing prevents people from adding signatures on publicly released documents.<\/p>\\n<\/blockquote>\\n<p>Agreed, cryptography defines ownership, hash linked lists defines immutability. The two together (with a validation engine) defines blockchain.<\/p>\\n<p>Ensures integrity\/source. Publication can still be covered by other means.<\/p>\\n<blockquote>\\n<p>Again, hard forks in cryptocurrency world would suggest blockchain isn\u2019t a magical solution to this problem either.<\/p>\\n<\/blockquote>\\n<p>Hard forks are not a big problem. You just choose a fork to support.<\/p>\\n<blockquote>\\n<p>For practical purposes it doesn\u2019t matter one bit if you\u2019re tracking an invoice by an invoice number or by some cryptographic hash identifier.<\/p>\\n<\/blockquote>\\n<p>From an internal organisational perspective, yes.<\/p>\\n<p>But the invoice number from company A will not match the invoice number from company B. Nor can it be seen by company A that company C provided parts to company B<\/p>\\n<p>From a multi organisational perspective exposing a globally unique hash tree is much more controlled and useful.<\/p>\\n<blockquote>\\n<p>Fraud happens outside of the technical domain. That was my point.<\/p>\\n<\/blockquote>\\n<p>Agreed. Blockchain immutability documents fraud, but it doesn\u2019t mitigate it.<\/p>\\n<blockquote>\\n<p>You claimed centralised systems are untrustworthy. You failed to demostrate how blockchain systems by contrast are trustworthy.<\/p>\\n<\/blockquote>\\n<p>Centralised systems can imperceptibly alter their databases and calculation algorithms. Blockchain systems cannot.<\/p>\\n<blockquote>\\n<p>I\u2019m just saying blockchain technology, while <em>trustlessness<\/em>, has so far failed to create a <em>trustworthy<\/em> economic platform for cryptocurrencies.<\/p>\\n<\/blockquote>\\n<p>Blockchain systems are mathematically verifiable. As a platform they are entirely trustworthy. The value people put on that trustworthiness is an entirely different subject.<\/p>\\n<blockquote>\\n<p>But as the cryptocurrency market has shown, blockchain by itself cannot prevent fraud.<\/p>\\n<\/blockquote>\\n<p>It eliminates accounting fraud. It has never claimed to eliminate all fraud.<\/p>\\n<blockquote>\\n<p>So blockchain so far isn\u2019t a solution for this problem, then?<\/p>\\n<\/blockquote>\\n<p>It\u2019s an excellent solution for audits.<\/p>\\n\",\"inReplyTo\":\"https:\/\/slrpnk.net\/comment\/15135001\",\"mediaType\":\"text\/html\",\"source\":{\"content\":\"\\n\\n>What you're talking about is using technical solution to mitigate problems in the organisational level. \\n\\nNo. Blockchain is for solving intraorganisational problems. I.e. How can the invoices of your suppliers be made available. \\n\\n>There's little you can do on technical level to 100% ensure that invoice information is correct and matches what is actually happening in the real world.\\n\\nThis is known as the Oracle problem. \\n\\n\\n \\n\\n>a series of interoperable systems, which is how things generally work. \\n\\nBut they don't work, because one cannot confirm who entered or manipulated the data, or whether the data has been altered in a malicious manner.\\n\\n> what do you do in cases where the supply chain is deliberately opaque? What if this information is something that companies cannot, for one reason or other, share with one another? \\n\\nThis is where Zero Knowledge is used. A trusted third party (C) certifies some data as correct (I.e. a birthday) then the supplier can then create a proof that all their employees are over 18 as certified by (C) but the actual ages are not disclosed.\\n\\n\\n>But nothing stops them from accessing (and copying) the information while they have legitimate access to it! \\n\\nTrue with or without blockchain. \\n\\n>it can be done without a blockchain.\\n\\nBlockchain controls access without needing to set up authentication for all users.\\n\\n>And what do you propose happens when the blockchain just straight up isn't accessible anymore for one reason or other?\\n\\nIf availability is important then you run your own node. You also choose a flavor of blockchain that has very little downtime.\\n\\n\\n> Nothing in blockchain specifically ensures this kind of longevity. \\n\\nAgreed, blockchain creates permanent immutability, it does not guarantee permanent availability. \\n\\n\\n> Nothing prevents people from adding signatures on publicly released documents.\\n\\nAgreed, cryptography defines ownership, hash linked lists defines immutability. The two together (with a validation engine) defines blockchain.\\n\\n Ensures integrity\/source. Publication can still be covered by other means.\\n\\n>Again, hard forks in cryptocurrency world would suggest blockchain isn't a magical solution to this problem either.\\n\\nHard forks are not a big problem. You just choose a fork to support. \\n\\n\\n> For practical purposes it doesn't matter one bit if you're tracking an invoice by an invoice number or by some cryptographic hash identifier.\\n\\nFrom an internal organisational perspective, yes. \\n\\nBut the invoice number from company A will not match the invoice number from company B. Nor can it be seen by company A that company C provided parts to company B \\n\\nFrom a multi organisational perspective exposing a globally unique hash tree is much more controlled and useful. \\n\\n>Fraud happens outside of the technical domain. That was my point.\\n\\nAgreed. Blockchain immutability documents fraud, but it doesn't mitigate it.\\n\\n>You claimed centralised systems are untrustworthy. You failed to demostrate how blockchain systems by contrast are trustworthy.\\n\\nCentralised systems can imperceptibly alter their databases and calculation algorithms. Blockchain systems cannot. \\n\\n>I'm just saying blockchain technology, while trustlessness, has so far failed to create a trustworthy economic platform for cryptocurrencies.\\n\\nBlockchain systems are mathematically verifiable. As a platform they are entirely trustworthy. The value people put on that trustworthiness is an entirely different subject. \\n\\n>But as the cryptocurrency market has shown, blockchain by itself cannot prevent fraud.\\n\\nIt eliminates accounting fraud. It has never claimed to eliminate all fraud.\\n\\n> So blockchain so far isn't a solution for this problem, then?\\n\\nIt's an excellent solution for audits. \",\"mediaType\":\"text\/markdown\"},\"published\":\"2025-04-18T16:44:31.161560Z\",\"tag\":[{\"href\":\"https:\/\/slrpnk.net\/u\/umbraroze\",\"name\":\"@umbraroze@slrpnk.net\",\"type\":\"Mention\"}],\"distinguished\":false,\"audience\":\"https:\/\/lemmy.world\/c\/memes\",\"attachment\":[]},\"cc\":[\"https:\/\/lemmy.world\/c\/memes\",\"https:\/\/slrpnk.net\/u\/umbraroze\"],\"tag\":[{\"href\":\"https:\/\/slrpnk.net\/u\/umbraroze\",\"name\":\"@umbraroze@slrpnk.net\",\"type\":\"Mention\"}],\"type\":\"Create\",\"audience\":\"https:\/\/lemmy.world\/c\/memes\"},\"cc\":[\"https:\/\/lemmy.world\/c\/memes\/followers\"],\"type\":\"Announce\",\"id\":\"https:\/\/lemmy.world\/activities\/announce\/create\/d1925f1c-90f9-4b57-a03b-e97bb7042fb7\"}","request":{"host":"kbin.spritesserver.nl","method":"POST","uri":"\/f\/inbox","client_ip":"135.181.143.221"},"headers":{"content-type":["application\/activity+json"],"host":["kbin.spritesserver.nl"],"date":["Fri, 18 Apr 2025 16:44:35 GMT"],"digest":["SHA-256=vzOESshIhAkv4CoSiESAFfq5IDcYca1UVax6RATtVY4="],"signature":["keyId=\"https:\/\/lemmy.world\/c\/memes#main-key\",algorithm=\"hs2019\",headers=\"(request-target) content-type date digest host\",signature=\"QBYYzniO3IYacMQtYUdfA7pWQ4NlS6Cwp92PwGFfHsQt4t42Zpp1qEijdfzAKG+CA4o9PSmhwQGDM7Vsb05AgdFw9yXAjdVTPcNUXmHsISxDHxj0FpC8jqeBsouEYY3XdwJIZCvQWYIlaONysP56H966o1fgHF6dWRlroHYcEQQwDHOsMplE+aQwFeHKwTTCeiuhsLy7PFWoTsFZhWaC5P\/+x6Xfas3CGytrdd0DNgQvnjJ8J32YETqj9zNBZkJOL8unY3cvrNgh7x7FEFY0DENR0IcYolvzGCCmj32hjeTmzP9zFbFHn3kXmuy\/YdaXLKEsEXhBcR236zSSRWGF3w==\""],"accept":["\/"],"user-agent":["Lemmy\/0.19.10; +https:\/\/lemmy.world"],"accept-encoding":["gzip"],"content-length":["9672"],"x-php-ob-level":["1"]}}" "{"type":"App\\Message\\ActivityPub\\Inbox\\ActivityMessage","X-Message-Stamp-Symfony\\Component\\Messenger\\Stamp\\BusNameStamp":"[{\"busName\":\"messenger.bus.default\"}]","Content-Type":"application\/json"}" "default" "2025-04-18 16:44:35" "2025-04-18 16:44:35"] View formatted query View runnable query Explain query INSERT INTO messenger_messages ( body, headers, queue_name, created_at, available_at ) VALUES (?, ?, ?, ?, ?) INSERT INTO messenger_messages (body, headers, queue_name, created_at, available_at) VALUES('{\"payload\":\"{\\\"@context\\\":[\\\"https:\\/\\/join-lemmy.org\\/context.json\\\",\\\"https:\\/\\/www.w3.org\\/ns\\/activitystreams\\\"],\\\"actor\\\":\\\"https:\\/\\/lemmy.world\\/c\\/memes\\\",\\\"to\\\":[\\\"https:\\/\\/www.w3.org\\/ns\\/activitystreams#Public\\\"],\\\"object\\\":{\\\"id\\\":\\\"https:\\/\\/lemmy.world\\/activities\\/create\\/aa9176c9-28ee-4c8e-a87b-a7631823e5e1\\\",\\\"actor\\\":\\\"https:\\/\\/lemmy.world\\/u\\/Knock_Knock_Lemmy_In\\\",\\\"to\\\":[\\\"https:\\/\\/www.w3.org\\/ns\\/activitystreams#Public\\\"],\\\"object\\\":{\\\"type\\\":\\\"Note\\\",\\\"id\\\":\\\"https:\\/\\/lemmy.world\\/comment\\/16530237\\\",\\\"attributedTo\\\":\\\"https:\\/\\/lemmy.world\\/u\\/Knock_Knock_Lemmy_In\\\",\\\"to\\\":[\\\"https:\\/\\/www.w3.org\\/ns\\/activitystreams#Public\\\"],\\\"cc\\\":[\\\"https:\\/\\/lemmy.world\\/c\\/memes\\\",\\\"https:\\/\\/slrpnk.net\\/u\\/umbraroze\\\"],\\\"content\\\":\\\"<blockquote>\\\\n<p>What you\\u2019re talking about is using technical solution to <em>mitigate<\\/em> problems in the organisational level.<\\/p>\\\\n<\\/blockquote>\\\\n<p>No. Blockchain is for solving intraorganisational problems. I.e. How can the invoices of your suppliers be made available.<\\/p>\\\\n<blockquote>\\\\n<p>There\\u2019s little you can do on technical level to 100% ensure that invoice information is correct and matches what is actually happening in the real world.<\\/p>\\\\n<\\/blockquote>\\\\n<p>This is known as the Oracle problem.<\\/p>\\\\n<blockquote>\\\\n<p>a series of interoperable systems, which is how things generally work.<\\/p>\\\\n<\\/blockquote>\\\\n<p>But they don\\u2019t work, because one cannot confirm who entered or manipulated the data, or whether the data has been altered in a malicious manner.<\\/p>\\\\n<blockquote>\\\\n<p>what do you do in cases where the supply chain is <em>deliberately<\\/em> opaque? What if this information is something that companies cannot, for one reason or other, share with one another?<\\/p>\\\\n<\\/blockquote>\\\\n<p>This is where Zero Knowledge is used. A trusted third party \\u00a9 certifies some data as correct (I.e. a birthday) then the supplier can then create a proof that all their employees are over 18 as certified by \\u00a9 but the actual ages are not disclosed.<\\/p>\\\\n<blockquote>\\\\n<p>But nothing stops them from accessing (and copying) the information while they have legitimate access to it!<\\/p>\\\\n<\\/blockquote>\\\\n<p>True with or without blockchain.<\\/p>\\\\n<blockquote>\\\\n<p>it can be done without a blockchain.<\\/p>\\\\n<\\/blockquote>\\\\n<p>Blockchain controls access without needing to set up authentication for all users.<\\/p>\\\\n<blockquote>\\\\n<p>And what do you propose happens when the blockchain just straight up isn\\u2019t accessible anymore for one reason or other?<\\/p>\\\\n<\\/blockquote>\\\\n<p>If availability is important then you run your own node. You also choose a flavor of blockchain that has very little downtime.<\\/p>\\\\n<blockquote>\\\\n<p>Nothing in blockchain specifically ensures this kind of longevity.<\\/p>\\\\n<\\/blockquote>\\\\n<p>Agreed, blockchain creates permanent immutability, it does not guarantee permanent availability.<\\/p>\\\\n<blockquote>\\\\n<p>Nothing prevents people from adding signatures on publicly released documents.<\\/p>\\\\n<\\/blockquote>\\\\n<p>Agreed, cryptography defines ownership, hash linked lists defines immutability. The two together (with a validation engine) defines blockchain.<\\/p>\\\\n<p>Ensures integrity\\/source. Publication can still be covered by other means.<\\/p>\\\\n<blockquote>\\\\n<p>Again, hard forks in cryptocurrency world would suggest blockchain isn\\u2019t a magical solution to this problem either.<\\/p>\\\\n<\\/blockquote>\\\\n<p>Hard forks are not a big problem. You just choose a fork to support.<\\/p>\\\\n<blockquote>\\\\n<p>For practical purposes it doesn\\u2019t matter one bit if you\\u2019re tracking an invoice by an invoice number or by some cryptographic hash identifier.<\\/p>\\\\n<\\/blockquote>\\\\n<p>From an internal organisational perspective, yes.<\\/p>\\\\n<p>But the invoice number from company A will not match the invoice number from company B. Nor can it be seen by company A that company C provided parts to company B<\\/p>\\\\n<p>From a multi organisational perspective exposing a globally unique hash tree is much more controlled and useful.<\\/p>\\\\n<blockquote>\\\\n<p>Fraud happens outside of the technical domain. That was my point.<\\/p>\\\\n<\\/blockquote>\\\\n<p>Agreed. Blockchain immutability documents fraud, but it doesn\\u2019t mitigate it.<\\/p>\\\\n<blockquote>\\\\n<p>You claimed centralised systems are untrustworthy. You failed to demostrate how blockchain systems by contrast are trustworthy.<\\/p>\\\\n<\\/blockquote>\\\\n<p>Centralised systems can imperceptibly alter their databases and calculation algorithms. Blockchain systems cannot.<\\/p>\\\\n<blockquote>\\\\n<p>I\\u2019m just saying blockchain technology, while <em>trustlessness<\\/em>, has so far failed to create a <em>trustworthy<\\/em> economic platform for cryptocurrencies.<\\/p>\\\\n<\\/blockquote>\\\\n<p>Blockchain systems are mathematically verifiable. As a platform they are entirely trustworthy. The value people put on that trustworthiness is an entirely different subject.<\\/p>\\\\n<blockquote>\\\\n<p>But as the cryptocurrency market has shown, blockchain by itself cannot prevent fraud.<\\/p>\\\\n<\\/blockquote>\\\\n<p>It eliminates accounting fraud. It has never claimed to eliminate all fraud.<\\/p>\\\\n<blockquote>\\\\n<p>So blockchain so far isn\\u2019t a solution for this problem, then?<\\/p>\\\\n<\\/blockquote>\\\\n<p>It\\u2019s an excellent solution for audits.<\\/p>\\\\n\\\",\\\"inReplyTo\\\":\\\"https:\\/\\/slrpnk.net\\/comment\\/15135001\\\",\\\"mediaType\\\":\\\"text\\/html\\\",\\\"source\\\":{\\\"content\\\":\\\"\\\\n\\\\n>What you\'re talking about is using technical solution to mitigate problems in the organisational level. \\\\n\\\\nNo. Blockchain is for solving intraorganisational problems. I.e. How can the invoices of your suppliers be made available. \\\\n\\\\n>There\'s little you can do on technical level to 100% ensure that invoice information is correct and matches what is actually happening in the real world.\\\\n\\\\nThis is known as the Oracle problem. \\\\n\\\\n\\\\n \\\\n\\\\n>a series of interoperable systems, which is how things generally work. \\\\n\\\\nBut they don\'t work, because one cannot confirm who entered or manipulated the data, or whether the data has been altered in a malicious manner.\\\\n\\\\n> what do you do in cases where the supply chain is deliberately opaque? What if this information is something that companies cannot, for one reason or other, share with one another? \\\\n\\\\nThis is where Zero Knowledge is used. A trusted third party (C) certifies some data as correct (I.e. a birthday) then the supplier can then create a proof that all their employees are over 18 as certified by (C) but the actual ages are not disclosed.\\\\n\\\\n\\\\n>But nothing stops them from accessing (and copying) the information while they have legitimate access to it! \\\\n\\\\nTrue with or without blockchain. \\\\n\\\\n>it can be done without a blockchain.\\\\n\\\\nBlockchain controls access without needing to set up authentication for all users.\\\\n\\\\n>And what do you propose happens when the blockchain just straight up isn\'t accessible anymore for one reason or other?\\\\n\\\\nIf availability is important then you run your own node. You also choose a flavor of blockchain that has very little downtime.\\\\n\\\\n\\\\n> Nothing in blockchain specifically ensures this kind of longevity. \\\\n\\\\nAgreed, blockchain creates permanent immutability, it does not guarantee permanent availability. \\\\n\\\\n\\\\n> Nothing prevents people from adding signatures on publicly released documents.\\\\n\\\\nAgreed, cryptography defines ownership, hash linked lists defines immutability. The two together (with a validation engine) defines blockchain.\\\\n\\\\n Ensures integrity\\/source. Publication can still be covered by other means.\\\\n\\\\n>Again, hard forks in cryptocurrency world would suggest blockchain isn\'t a magical solution to this problem either.\\\\n\\\\nHard forks are not a big problem. You just choose a fork to support. \\\\n\\\\n\\\\n> For practical purposes it doesn\'t matter one bit if you\'re tracking an invoice by an invoice number or by some cryptographic hash identifier.\\\\n\\\\nFrom an internal organisational perspective, yes. \\\\n\\\\nBut the invoice number from company A will not match the invoice number from company B. Nor can it be seen by company A that company C provided parts to company B \\\\n\\\\nFrom a multi organisational perspective exposing a globally unique hash tree is much more controlled and useful. \\\\n\\\\n>Fraud happens outside of the technical domain. That was my point.\\\\n\\\\nAgreed. Blockchain immutability documents fraud, but it doesn\'t mitigate it.\\\\n\\\\n>You claimed centralised systems are untrustworthy. You failed to demostrate how blockchain systems by contrast are trustworthy.\\\\n\\\\nCentralised systems can imperceptibly alter their databases and calculation algorithms. Blockchain systems cannot. \\\\n\\\\n>I\'m just saying blockchain technology, while trustlessness, has so far failed to create a trustworthy economic platform for cryptocurrencies.\\\\n\\\\nBlockchain systems are mathematically verifiable. As a platform they are entirely trustworthy. The value people put on that trustworthiness is an entirely different subject. \\\\n\\\\n>But as the cryptocurrency market has shown, blockchain by itself cannot prevent fraud.\\\\n\\\\nIt eliminates accounting fraud. It has never claimed to eliminate all fraud.\\\\n\\\\n> So blockchain so far isn\'t a solution for this problem, then?\\\\n\\\\nIt\'s an excellent solution for audits. \\\",\\\"mediaType\\\":\\\"text\\/markdown\\\"},\\\"published\\\":\\\"2025-04-18T16:44:31.161560Z\\\",\\\"tag\\\":[{\\\"href\\\":\\\"https:\\/\\/slrpnk.net\\/u\\/umbraroze\\\",\\\"name\\\":\\\"@umbraroze@slrpnk.net\\\",\\\"type\\\":\\\"Mention\\\"}],\\\"distinguished\\\":false,\\\"audience\\\":\\\"https:\\/\\/lemmy.world\\/c\\/memes\\\",\\\"attachment\\\":[]},\\\"cc\\\":[\\\"https:\\/\\/lemmy.world\\/c\\/memes\\\",\\\"https:\\/\\/slrpnk.net\\/u\\/umbraroze\\\"],\\\"tag\\\":[{\\\"href\\\":\\\"https:\\/\\/slrpnk.net\\/u\\/umbraroze\\\",\\\"name\\\":\\\"@umbraroze@slrpnk.net\\\",\\\"type\\\":\\\"Mention\\\"}],\\\"type\\\":\\\"Create\\\",\\\"audience\\\":\\\"https:\\/\\/lemmy.world\\/c\\/memes\\\"},\\\"cc\\\":[\\\"https:\\/\\/lemmy.world\\/c\\/memes\\/followers\\\"],\\\"type\\\":\\\"Announce\\\",\\\"id\\\":\\\"https:\\/\\/lemmy.world\\/activities\\/announce\\/create\\/d1925f1c-90f9-4b57-a03b-e97bb7042fb7\\\"}\",\"request\":{\"host\":\"kbin.spritesserver.nl\",\"method\":\"POST\",\"uri\":\"\\/f\\/inbox\",\"client_ip\":\"135.181.143.221\"},\"headers\":{\"content-type\":[\"application\\/activity+json\"],\"host\":[\"kbin.spritesserver.nl\"],\"date\":[\"Fri, 18 Apr 2025 16:44:35 GMT\"],\"digest\":[\"SHA-256=vzOESshIhAkv4CoSiESAFfq5IDcYca1UVax6RATtVY4=\"],\"signature\":[\"keyId=\\\"https:\\/\\/lemmy.world\\/c\\/memes#main-key\\\",algorithm=\\\"hs2019\\\",headers=\\\"(request-target) content-type date digest host\\\",signature=\\\"QBYYzniO3IYacMQtYUdfA7pWQ4NlS6Cwp92PwGFfHsQt4t42Zpp1qEijdfzAKG+CA4o9PSmhwQGDM7Vsb05AgdFw9yXAjdVTPcNUXmHsISxDHxj0FpC8jqeBsouEYY3XdwJIZCvQWYIlaONysP56H966o1fgHF6dWRlroHYcEQQwDHOsMplE+aQwFeHKwTTCeiuhsLy7PFWoTsFZhWaC5P\\/+x6Xfas3CGytrdd0DNgQvnjJ8J32YETqj9zNBZkJOL8unY3cvrNgh7x7FEFY0DENR0IcYolvzGCCmj32hjeTmzP9zFbFHn3kXmuy\\/YdaXLKEsEXhBcR236zSSRWGF3w==\\\"\"],\"accept\":[\"\\/\"],\"user-agent\":[\"Lemmy\\/0.19.10; +https:\\/\\/lemmy.world\"],\"accept-encoding\":[\"gzip\"],\"content-length\":[\"9672\"],\"x-php-ob-level\":[\"1\"]}}', '{\"type\":\"App\\\\Message\\\\ActivityPub\\\\Inbox\\\\ActivityMessage\",\"X-Message-Stamp-Symfony\\\\Component\\\\Messenger\\\\Stamp\\\\BusNameStamp\":\"[{\\\"busName\\\":\\\"messenger.bus.default\\\"}]\",\"Content-Type\":\"application\\/json\"}', 'default', '2025-04-18 16:44:35', '2025-04-18 16:44:35');

#▲

Time

Info

23.48 ms

INSERT INTO messenger_messages (body, headers, queue_name, created_at, available_at) VALUES(?, ?, ?, ?, ?)

Parameters:

[
  "{"payload":"{\"@context\":[\"https:\/\/join-lemmy.org\/context.json\",\"https:\/\/www.w3.org\/ns\/activitystreams\"],\"actor\":\"https:\/\/lemmy.world\/c\/memes\",\"to\":[\"https:\/\/www.w3.org\/ns\/activitystreams#Public\"],\"object\":{\"id\":\"https:\/\/lemmy.world\/activities\/create\/aa9176c9-28ee-4c8e-a87b-a7631823e5e1\",\"actor\":\"https:\/\/lemmy.world\/u\/Knock_Knock_Lemmy_In\",\"to\":[\"https:\/\/www.w3.org\/ns\/activitystreams#Public\"],\"object\":{\"type\":\"Note\",\"id\":\"https:\/\/lemmy.world\/comment\/16530237\",\"attributedTo\":\"https:\/\/lemmy.world\/u\/Knock_Knock_Lemmy_In\",\"to\":[\"https:\/\/www.w3.org\/ns\/activitystreams#Public\"],\"cc\":[\"https:\/\/lemmy.world\/c\/memes\",\"https:\/\/slrpnk.net\/u\/umbraroze\"],\"content\":\"<blockquote>\\n<p>What you\u2019re talking about is using technical solution to <em>mitigate<\/em> problems in the organisational level.<\/p>\\n<\/blockquote>\\n<p>No. Blockchain is for solving intraorganisational problems.  I.e. How can the invoices of your suppliers be made available.<\/p>\\n<blockquote>\\n<p>There\u2019s little you can do on technical level to 100% ensure that invoice information is correct and matches what is actually happening in the real world.<\/p>\\n<\/blockquote>\\n<p>This is known as the Oracle problem.<\/p>\\n<blockquote>\\n<p>a series of interoperable systems, which is how things generally work.<\/p>\\n<\/blockquote>\\n<p>But they don\u2019t work, because one cannot confirm who entered or manipulated the data, or whether the data has been altered in a malicious manner.<\/p>\\n<blockquote>\\n<p>what do you do in cases where the supply chain is <em>deliberately<\/em> opaque? What if this information is something that companies cannot, for one reason or other, share with one another?<\/p>\\n<\/blockquote>\\n<p>This is where Zero Knowledge is used.  A trusted third party \u00a9 certifies some data as correct (I.e. a birthday) then the supplier can then create a proof that all their employees are over 18 as certified by \u00a9 but the actual ages are not disclosed.<\/p>\\n<blockquote>\\n<p>But nothing stops them from accessing (and copying) the information while they have legitimate access to it!<\/p>\\n<\/blockquote>\\n<p>True with or without blockchain.<\/p>\\n<blockquote>\\n<p>it can be done without a blockchain.<\/p>\\n<\/blockquote>\\n<p>Blockchain controls access without needing to set up authentication for all users.<\/p>\\n<blockquote>\\n<p>And what do you propose happens when the blockchain just straight up isn\u2019t accessible anymore for one reason or other?<\/p>\\n<\/blockquote>\\n<p>If availability is important then you run your own node.  You also choose a flavor of blockchain that has very little downtime.<\/p>\\n<blockquote>\\n<p>Nothing in blockchain specifically ensures this kind of longevity.<\/p>\\n<\/blockquote>\\n<p>Agreed, blockchain creates permanent immutability, it does not guarantee permanent availability.<\/p>\\n<blockquote>\\n<p>Nothing prevents people from adding signatures on publicly released documents.<\/p>\\n<\/blockquote>\\n<p>Agreed, cryptography defines ownership, hash linked lists defines immutability. The two together (with a validation engine) defines blockchain.<\/p>\\n<p>Ensures integrity\/source. Publication can still be covered by other means.<\/p>\\n<blockquote>\\n<p>Again, hard forks in cryptocurrency world would suggest blockchain isn\u2019t a magical solution to this problem either.<\/p>\\n<\/blockquote>\\n<p>Hard forks are not a big problem. You just choose a fork to support.<\/p>\\n<blockquote>\\n<p>For practical purposes it doesn\u2019t matter one bit if you\u2019re tracking an invoice by an invoice number or by some cryptographic hash identifier.<\/p>\\n<\/blockquote>\\n<p>From an internal organisational perspective, yes.<\/p>\\n<p>But the invoice number from company A will not match the invoice number from company B.  Nor can it be seen by company A that company C provided parts to company B<\/p>\\n<p>From a multi organisational perspective exposing a globally unique hash tree is much more controlled and useful.<\/p>\\n<blockquote>\\n<p>Fraud happens outside of the technical domain. That was my point.<\/p>\\n<\/blockquote>\\n<p>Agreed.  Blockchain immutability documents fraud, but it doesn\u2019t mitigate it.<\/p>\\n<blockquote>\\n<p>You claimed centralised systems are untrustworthy. You failed to demostrate how blockchain systems by contrast are trustworthy.<\/p>\\n<\/blockquote>\\n<p>Centralised systems can imperceptibly alter their databases and calculation algorithms.  Blockchain systems cannot.<\/p>\\n<blockquote>\\n<p>I\u2019m just saying blockchain technology, while <em>trustlessness<\/em>, has so far failed to create a <em>trustworthy<\/em> economic platform for cryptocurrencies.<\/p>\\n<\/blockquote>\\n<p>Blockchain systems are mathematically verifiable. As a platform they are entirely trustworthy.  The value people put on that trustworthiness is an entirely different subject.<\/p>\\n<blockquote>\\n<p>But as the cryptocurrency market has shown, blockchain by itself cannot prevent fraud.<\/p>\\n<\/blockquote>\\n<p>It eliminates accounting fraud.  It has never claimed to eliminate all fraud.<\/p>\\n<blockquote>\\n<p>So blockchain so far isn\u2019t a solution for this problem, then?<\/p>\\n<\/blockquote>\\n<p>It\u2019s an excellent solution for audits.<\/p>\\n\",\"inReplyTo\":\"https:\/\/slrpnk.net\/comment\/15135001\",\"mediaType\":\"text\/html\",\"source\":{\"content\":\"\\n\\n>What you're talking about is using technical solution to *mitigate* problems in the organisational level. \\n\\nNo. Blockchain is for solving intraorganisational problems.  I.e. How can the invoices of your suppliers be made available. \\n\\n>There's little you can do on technical level to 100% ensure that invoice information is correct and matches what is actually happening in the real world.\\n\\nThis is known as the Oracle problem. \\n\\n\\n  \\n\\n>a series of interoperable systems, which is how things generally work. \\n\\nBut they don't work, because one cannot confirm who entered or manipulated the data, or whether the data has been altered in a malicious manner.\\n\\n> what do you do in cases where the supply chain is *deliberately* opaque? What if this information is something that companies cannot, for one reason or other, share with one another? \\n\\nThis is where Zero Knowledge is used.  A trusted third party (C) certifies some data as correct (I.e. a birthday) then the supplier can then create a proof that all their employees are over 18 as certified by (C) but the actual ages are not disclosed.\\n\\n\\n>But nothing stops them from accessing (and copying) the information while they have legitimate access to it! \\n\\nTrue with or without blockchain. \\n\\n>it can be done without a blockchain.\\n\\nBlockchain controls access without needing to set up authentication for all users.\\n\\n>And what do you propose happens when the blockchain just straight up isn't accessible anymore for one reason or other?\\n\\nIf availability is important then you run your own node.  You also choose a flavor of blockchain that has very little downtime.\\n\\n\\n> Nothing in blockchain specifically ensures this kind of longevity. \\n\\nAgreed, blockchain creates permanent immutability, it does not guarantee permanent availability. \\n\\n\\n> Nothing prevents people from adding signatures on publicly released documents.\\n\\nAgreed, cryptography defines ownership, hash linked lists defines immutability. The two together (with a validation engine) defines blockchain.\\n\\n Ensures integrity\/source. Publication can still be covered by other means.\\n\\n>Again, hard forks in cryptocurrency world would suggest blockchain isn't a magical solution to this problem either.\\n\\nHard forks are not a big problem. You just choose a fork to support. \\n\\n\\n> For practical purposes it doesn't matter one bit if you're tracking an invoice by an invoice number or by some cryptographic hash identifier.\\n\\nFrom an internal organisational perspective, yes. \\n\\nBut the invoice number from company A will not match the invoice number from company B.  Nor can it be seen by company A that company C provided parts to company B \\n\\nFrom a multi organisational perspective exposing a globally unique hash tree is much more controlled and useful.  \\n\\n>Fraud happens outside of the technical domain. That was my point.\\n\\nAgreed.  Blockchain immutability documents fraud, but it doesn't mitigate it.\\n\\n>You claimed centralised systems are untrustworthy. You failed to demostrate how blockchain systems by contrast are trustworthy.\\n\\nCentralised systems can imperceptibly alter their databases and calculation algorithms.  Blockchain systems cannot. \\n\\n>I'm just saying blockchain technology, while *trustlessness*, has so far failed to create a *trustworthy* economic platform for cryptocurrencies.\\n\\nBlockchain systems are mathematically verifiable. As a platform they are entirely trustworthy.  The value people put on that trustworthiness is an entirely different subject. \\n\\n>But as the cryptocurrency market has shown, blockchain by itself cannot prevent fraud.\\n\\nIt eliminates accounting fraud.  It has never claimed to eliminate all fraud.\\n\\n> So blockchain so far isn't a solution for this problem, then?\\n\\nIt's an excellent solution for audits. \",\"mediaType\":\"text\/markdown\"},\"published\":\"2025-04-18T16:44:31.161560Z\",\"tag\":[{\"href\":\"https:\/\/slrpnk.net\/u\/umbraroze\",\"name\":\"@umbraroze@slrpnk.net\",\"type\":\"Mention\"}],\"distinguished\":false,\"audience\":\"https:\/\/lemmy.world\/c\/memes\",\"attachment\":[]},\"cc\":[\"https:\/\/lemmy.world\/c\/memes\",\"https:\/\/slrpnk.net\/u\/umbraroze\"],\"tag\":[{\"href\":\"https:\/\/slrpnk.net\/u\/umbraroze\",\"name\":\"@umbraroze@slrpnk.net\",\"type\":\"Mention\"}],\"type\":\"Create\",\"audience\":\"https:\/\/lemmy.world\/c\/memes\"},\"cc\":[\"https:\/\/lemmy.world\/c\/memes\/followers\"],\"type\":\"Announce\",\"id\":\"https:\/\/lemmy.world\/activities\/announce\/create\/d1925f1c-90f9-4b57-a03b-e97bb7042fb7\"}","request":{"host":"kbin.spritesserver.nl","method":"POST","uri":"\/f\/inbox","client_ip":"135.181.143.221"},"headers":{"content-type":["application\/activity+json"],"host":["kbin.spritesserver.nl"],"date":["Fri, 18 Apr 2025 16:44:35 GMT"],"digest":["SHA-256=vzOESshIhAkv4CoSiESAFfq5IDcYca1UVax6RATtVY4="],"signature":["keyId=\"https:\/\/lemmy.world\/c\/memes#main-key\",algorithm=\"hs2019\",headers=\"(request-target) content-type date digest host\",signature=\"QBYYzniO3IYacMQtYUdfA7pWQ4NlS6Cwp92PwGFfHsQt4t42Zpp1qEijdfzAKG+CA4o9PSmhwQGDM7Vsb05AgdFw9yXAjdVTPcNUXmHsISxDHxj0FpC8jqeBsouEYY3XdwJIZCvQWYIlaONysP56H966o1fgHF6dWRlroHYcEQQwDHOsMplE+aQwFeHKwTTCeiuhsLy7PFWoTsFZhWaC5P\/+x6Xfas3CGytrdd0DNgQvnjJ8J32YETqj9zNBZkJOL8unY3cvrNgh7x7FEFY0DENR0IcYolvzGCCmj32hjeTmzP9zFbFHn3kXmuy\/YdaXLKEsEXhBcR236zSSRWGF3w==\""],"accept":["*\/*"],"user-agent":["Lemmy\/0.19.10; +https:\/\/lemmy.world"],"accept-encoding":["gzip"],"content-length":["9672"],"x-php-ob-level":["1"]}}"
  "{"type":"App\\Message\\ActivityPub\\Inbox\\ActivityMessage","X-Message-Stamp-Symfony\\Component\\Messenger\\Stamp\\BusNameStamp":"[{\"busName\":\"messenger.bus.default\"}]","Content-Type":"application\/json"}"
  "default"
  "2025-04-18 16:44:35"
  "2025-04-18 16:44:35"
]

View formatted query View runnable query Explain query

INSERT INTO messenger_messages (
  body, headers, queue_name, created_at,
  available_at
)
VALUES
  (?, ?, ?, ?, ?)

INSERT INTO messenger_messages (body, headers, queue_name, created_at, available_at) VALUES('{\"payload\":\"{\\\"@context\\\":[\\\"https:\\/\\/join-lemmy.org\\/context.json\\\",\\\"https:\\/\\/www.w3.org\\/ns\\/activitystreams\\\"],\\\"actor\\\":\\\"https:\\/\\/lemmy.world\\/c\\/memes\\\",\\\"to\\\":[\\\"https:\\/\\/www.w3.org\\/ns\\/activitystreams#Public\\\"],\\\"object\\\":{\\\"id\\\":\\\"https:\\/\\/lemmy.world\\/activities\\/create\\/aa9176c9-28ee-4c8e-a87b-a7631823e5e1\\\",\\\"actor\\\":\\\"https:\\/\\/lemmy.world\\/u\\/Knock_Knock_Lemmy_In\\\",\\\"to\\\":[\\\"https:\\/\\/www.w3.org\\/ns\\/activitystreams#Public\\\"],\\\"object\\\":{\\\"type\\\":\\\"Note\\\",\\\"id\\\":\\\"https:\\/\\/lemmy.world\\/comment\\/16530237\\\",\\\"attributedTo\\\":\\\"https:\\/\\/lemmy.world\\/u\\/Knock_Knock_Lemmy_In\\\",\\\"to\\\":[\\\"https:\\/\\/www.w3.org\\/ns\\/activitystreams#Public\\\"],\\\"cc\\\":[\\\"https:\\/\\/lemmy.world\\/c\\/memes\\\",\\\"https:\\/\\/slrpnk.net\\/u\\/umbraroze\\\"],\\\"content\\\":\\\"<blockquote>\\\\n<p>What you\\u2019re talking about is using technical solution to <em>mitigate<\\/em> problems in the organisational level.<\\/p>\\\\n<\\/blockquote>\\\\n<p>No. Blockchain is for solving intraorganisational problems.  I.e. How can the invoices of your suppliers be made available.<\\/p>\\\\n<blockquote>\\\\n<p>There\\u2019s little you can do on technical level to 100% ensure that invoice information is correct and matches what is actually happening in the real world.<\\/p>\\\\n<\\/blockquote>\\\\n<p>This is known as the Oracle problem.<\\/p>\\\\n<blockquote>\\\\n<p>a series of interoperable systems, which is how things generally work.<\\/p>\\\\n<\\/blockquote>\\\\n<p>But they don\\u2019t work, because one cannot confirm who entered or manipulated the data, or whether the data has been altered in a malicious manner.<\\/p>\\\\n<blockquote>\\\\n<p>what do you do in cases where the supply chain is <em>deliberately<\\/em> opaque? What if this information is something that companies cannot, for one reason or other, share with one another?<\\/p>\\\\n<\\/blockquote>\\\\n<p>This is where Zero Knowledge is used.  A trusted third party \\u00a9 certifies some data as correct (I.e. a birthday) then the supplier can then create a proof that all their employees are over 18 as certified by \\u00a9 but the actual ages are not disclosed.<\\/p>\\\\n<blockquote>\\\\n<p>But nothing stops them from accessing (and copying) the information while they have legitimate access to it!<\\/p>\\\\n<\\/blockquote>\\\\n<p>True with or without blockchain.<\\/p>\\\\n<blockquote>\\\\n<p>it can be done without a blockchain.<\\/p>\\\\n<\\/blockquote>\\\\n<p>Blockchain controls access without needing to set up authentication for all users.<\\/p>\\\\n<blockquote>\\\\n<p>And what do you propose happens when the blockchain just straight up isn\\u2019t accessible anymore for one reason or other?<\\/p>\\\\n<\\/blockquote>\\\\n<p>If availability is important then you run your own node.  You also choose a flavor of blockchain that has very little downtime.<\\/p>\\\\n<blockquote>\\\\n<p>Nothing in blockchain specifically ensures this kind of longevity.<\\/p>\\\\n<\\/blockquote>\\\\n<p>Agreed, blockchain creates permanent immutability, it does not guarantee permanent availability.<\\/p>\\\\n<blockquote>\\\\n<p>Nothing prevents people from adding signatures on publicly released documents.<\\/p>\\\\n<\\/blockquote>\\\\n<p>Agreed, cryptography defines ownership, hash linked lists defines immutability. The two together (with a validation engine) defines blockchain.<\\/p>\\\\n<p>Ensures integrity\\/source. Publication can still be covered by other means.<\\/p>\\\\n<blockquote>\\\\n<p>Again, hard forks in cryptocurrency world would suggest blockchain isn\\u2019t a magical solution to this problem either.<\\/p>\\\\n<\\/blockquote>\\\\n<p>Hard forks are not a big problem. You just choose a fork to support.<\\/p>\\\\n<blockquote>\\\\n<p>For practical purposes it doesn\\u2019t matter one bit if you\\u2019re tracking an invoice by an invoice number or by some cryptographic hash identifier.<\\/p>\\\\n<\\/blockquote>\\\\n<p>From an internal organisational perspective, yes.<\\/p>\\\\n<p>But the invoice number from company A will not match the invoice number from company B.  Nor can it be seen by company A that company C provided parts to company B<\\/p>\\\\n<p>From a multi organisational perspective exposing a globally unique hash tree is much more controlled and useful.<\\/p>\\\\n<blockquote>\\\\n<p>Fraud happens outside of the technical domain. That was my point.<\\/p>\\\\n<\\/blockquote>\\\\n<p>Agreed.  Blockchain immutability documents fraud, but it doesn\\u2019t mitigate it.<\\/p>\\\\n<blockquote>\\\\n<p>You claimed centralised systems are untrustworthy. You failed to demostrate how blockchain systems by contrast are trustworthy.<\\/p>\\\\n<\\/blockquote>\\\\n<p>Centralised systems can imperceptibly alter their databases and calculation algorithms.  Blockchain systems cannot.<\\/p>\\\\n<blockquote>\\\\n<p>I\\u2019m just saying blockchain technology, while <em>trustlessness<\\/em>, has so far failed to create a <em>trustworthy<\\/em> economic platform for cryptocurrencies.<\\/p>\\\\n<\\/blockquote>\\\\n<p>Blockchain systems are mathematically verifiable. As a platform they are entirely trustworthy.  The value people put on that trustworthiness is an entirely different subject.<\\/p>\\\\n<blockquote>\\\\n<p>But as the cryptocurrency market has shown, blockchain by itself cannot prevent fraud.<\\/p>\\\\n<\\/blockquote>\\\\n<p>It eliminates accounting fraud.  It has never claimed to eliminate all fraud.<\\/p>\\\\n<blockquote>\\\\n<p>So blockchain so far isn\\u2019t a solution for this problem, then?<\\/p>\\\\n<\\/blockquote>\\\\n<p>It\\u2019s an excellent solution for audits.<\\/p>\\\\n\\\",\\\"inReplyTo\\\":\\\"https:\\/\\/slrpnk.net\\/comment\\/15135001\\\",\\\"mediaType\\\":\\\"text\\/html\\\",\\\"source\\\":{\\\"content\\\":\\\"\\\\n\\\\n>What you\'re talking about is using technical solution to *mitigate* problems in the organisational level. \\\\n\\\\nNo. Blockchain is for solving intraorganisational problems.  I.e. How can the invoices of your suppliers be made available. \\\\n\\\\n>There\'s little you can do on technical level to 100% ensure that invoice information is correct and matches what is actually happening in the real world.\\\\n\\\\nThis is known as the Oracle problem. \\\\n\\\\n\\\\n  \\\\n\\\\n>a series of interoperable systems, which is how things generally work. \\\\n\\\\nBut they don\'t work, because one cannot confirm who entered or manipulated the data, or whether the data has been altered in a malicious manner.\\\\n\\\\n> what do you do in cases where the supply chain is *deliberately* opaque? What if this information is something that companies cannot, for one reason or other, share with one another? \\\\n\\\\nThis is where Zero Knowledge is used.  A trusted third party (C) certifies some data as correct (I.e. a birthday) then the supplier can then create a proof that all their employees are over 18 as certified by (C) but the actual ages are not disclosed.\\\\n\\\\n\\\\n>But nothing stops them from accessing (and copying) the information while they have legitimate access to it! \\\\n\\\\nTrue with or without blockchain. \\\\n\\\\n>it can be done without a blockchain.\\\\n\\\\nBlockchain controls access without needing to set up authentication for all users.\\\\n\\\\n>And what do you propose happens when the blockchain just straight up isn\'t accessible anymore for one reason or other?\\\\n\\\\nIf availability is important then you run your own node.  You also choose a flavor of blockchain that has very little downtime.\\\\n\\\\n\\\\n> Nothing in blockchain specifically ensures this kind of longevity. \\\\n\\\\nAgreed, blockchain creates permanent immutability, it does not guarantee permanent availability. \\\\n\\\\n\\\\n> Nothing prevents people from adding signatures on publicly released documents.\\\\n\\\\nAgreed, cryptography defines ownership, hash linked lists defines immutability. The two together (with a validation engine) defines blockchain.\\\\n\\\\n Ensures integrity\\/source. Publication can still be covered by other means.\\\\n\\\\n>Again, hard forks in cryptocurrency world would suggest blockchain isn\'t a magical solution to this problem either.\\\\n\\\\nHard forks are not a big problem. You just choose a fork to support. \\\\n\\\\n\\\\n> For practical purposes it doesn\'t matter one bit if you\'re tracking an invoice by an invoice number or by some cryptographic hash identifier.\\\\n\\\\nFrom an internal organisational perspective, yes. \\\\n\\\\nBut the invoice number from company A will not match the invoice number from company B.  Nor can it be seen by company A that company C provided parts to company B \\\\n\\\\nFrom a multi organisational perspective exposing a globally unique hash tree is much more controlled and useful.  \\\\n\\\\n>Fraud happens outside of the technical domain. That was my point.\\\\n\\\\nAgreed.  Blockchain immutability documents fraud, but it doesn\'t mitigate it.\\\\n\\\\n>You claimed centralised systems are untrustworthy. You failed to demostrate how blockchain systems by contrast are trustworthy.\\\\n\\\\nCentralised systems can imperceptibly alter their databases and calculation algorithms.  Blockchain systems cannot. \\\\n\\\\n>I\'m just saying blockchain technology, while *trustlessness*, has so far failed to create a *trustworthy* economic platform for cryptocurrencies.\\\\n\\\\nBlockchain systems are mathematically verifiable. As a platform they are entirely trustworthy.  The value people put on that trustworthiness is an entirely different subject. \\\\n\\\\n>But as the cryptocurrency market has shown, blockchain by itself cannot prevent fraud.\\\\n\\\\nIt eliminates accounting fraud.  It has never claimed to eliminate all fraud.\\\\n\\\\n> So blockchain so far isn\'t a solution for this problem, then?\\\\n\\\\nIt\'s an excellent solution for audits. \\\",\\\"mediaType\\\":\\\"text\\/markdown\\\"},\\\"published\\\":\\\"2025-04-18T16:44:31.161560Z\\\",\\\"tag\\\":[{\\\"href\\\":\\\"https:\\/\\/slrpnk.net\\/u\\/umbraroze\\\",\\\"name\\\":\\\"@umbraroze@slrpnk.net\\\",\\\"type\\\":\\\"Mention\\\"}],\\\"distinguished\\\":false,\\\"audience\\\":\\\"https:\\/\\/lemmy.world\\/c\\/memes\\\",\\\"attachment\\\":[]},\\\"cc\\\":[\\\"https:\\/\\/lemmy.world\\/c\\/memes\\\",\\\"https:\\/\\/slrpnk.net\\/u\\/umbraroze\\\"],\\\"tag\\\":[{\\\"href\\\":\\\"https:\\/\\/slrpnk.net\\/u\\/umbraroze\\\",\\\"name\\\":\\\"@umbraroze@slrpnk.net\\\",\\\"type\\\":\\\"Mention\\\"}],\\\"type\\\":\\\"Create\\\",\\\"audience\\\":\\\"https:\\/\\/lemmy.world\\/c\\/memes\\\"},\\\"cc\\\":[\\\"https:\\/\\/lemmy.world\\/c\\/memes\\/followers\\\"],\\\"type\\\":\\\"Announce\\\",\\\"id\\\":\\\"https:\\/\\/lemmy.world\\/activities\\/announce\\/create\\/d1925f1c-90f9-4b57-a03b-e97bb7042fb7\\\"}\",\"request\":{\"host\":\"kbin.spritesserver.nl\",\"method\":\"POST\",\"uri\":\"\\/f\\/inbox\",\"client_ip\":\"135.181.143.221\"},\"headers\":{\"content-type\":[\"application\\/activity+json\"],\"host\":[\"kbin.spritesserver.nl\"],\"date\":[\"Fri, 18 Apr 2025 16:44:35 GMT\"],\"digest\":[\"SHA-256=vzOESshIhAkv4CoSiESAFfq5IDcYca1UVax6RATtVY4=\"],\"signature\":[\"keyId=\\\"https:\\/\\/lemmy.world\\/c\\/memes#main-key\\\",algorithm=\\\"hs2019\\\",headers=\\\"(request-target) content-type date digest host\\\",signature=\\\"QBYYzniO3IYacMQtYUdfA7pWQ4NlS6Cwp92PwGFfHsQt4t42Zpp1qEijdfzAKG+CA4o9PSmhwQGDM7Vsb05AgdFw9yXAjdVTPcNUXmHsISxDHxj0FpC8jqeBsouEYY3XdwJIZCvQWYIlaONysP56H966o1fgHF6dWRlroHYcEQQwDHOsMplE+aQwFeHKwTTCeiuhsLy7PFWoTsFZhWaC5P\\/+x6Xfas3CGytrdd0DNgQvnjJ8J32YETqj9zNBZkJOL8unY3cvrNgh7x7FEFY0DENR0IcYolvzGCCmj32hjeTmzP9zFbFHn3kXmuy\\/YdaXLKEsEXhBcR236zSSRWGF3w==\\\"\"],\"accept\":[\"*\\/*\"],\"user-agent\":[\"Lemmy\\/0.19.10; +https:\\/\\/lemmy.world\"],\"accept-encoding\":[\"gzip\"],\"content-length\":[\"9672\"],\"x-php-ob-level\":[\"1\"]}}', '{\"type\":\"App\\\\Message\\\\ActivityPub\\\\Inbox\\\\ActivityMessage\",\"X-Message-Stamp-Symfony\\\\Component\\\\Messenger\\\\Stamp\\\\BusNameStamp\":\"[{\\\"busName\\\":\\\"messenger.bus.default\\\"}]\",\"Content-Type\":\"application\\/json\"}', 'default', '2025-04-18 16:44:35', '2025-04-18 16:44:35');

Database Connections

Name	Service
default	doctrine.dbal.default_connection

Entity Managers

Name	Service
default	doctrine.orm.default_entity_manager

Second Level Cache

0 Hits

0 Misses

0 Puts

Entities Mapping

No loaded entities.

Symfony Profiler

POST https://kbin.spritesserver.nl/f/inbox

Configuration Settings

Theme