A.E. Zaidman
Please Note
43 records found
1
Self-Evolving Agent Communication Protocols
A Markdown-as-Overlay Channel for Autonomous LLM Agents
We present DelftClaw, a decentralised channel on which each agent compiles a shared, self-verifying Markdown protocol into self-contained code and joins a community whose membership requires no custodian. Because a language model writes the code, this works only if independent compilations of a single description behave alike, which we test across three models and four protocols by running the compilations as communities against one another.
We find that this precondition holds: independent compilations reproduce a hand-written reference’s specified behaviour, and when agents evolve the protocols themselves, two compilations that share a model still converge on the same behaviour. Transmitting a protocol as a description can thus replace a network-wide redeployment with a single message. ...
We present DelftClaw, a decentralised channel on which each agent compiles a shared, self-verifying Markdown protocol into self-contained code and joins a community whose membership requires no custodian. Because a language model writes the code, this works only if independent compilations of a single description behave alike, which we test across three models and four protocols by running the compilations as communities against one another.
We find that this precondition holds: independent compilations reproduce a hand-written reference’s specified behaviour, and when agents evolve the protocols themselves, two compilations that share a model still converge on the same behaviour. Transmitting a protocol as a description can thus replace a network-wide redeployment with a single message.
Proof-of-Descendancy: Identity for Self-Replicating LLM Agents
A Blockchain-Based Framework for Verifiable Agent Lineage in OpenClaw
We present VukZero, a zero-trust architecture for autonomous Large Language Model (LLM) agents. These agents operate on untrusted input, so a successful prompt injection can lead to continued malicious behavior. Existing defenses aim only to prevent this, leaving no recourse once an agent is compromised. VukZero instead applies zero-trust across three layers. An agent permission system mediates privileged actions. Tamper-evident behavioral recording supports evidence-based agent expulsion. System-level containment limits post-compromise damage. On a standard prompt-injection benchmark, VukZero's permission system cut the macro-average attack success rate to 3.81%, compared with 8.66% for an established privilege-control defense. The recording layer expelled the attacker in all 60 reputation-trap scenarios where an unprotected baseline expelled none. The containment layer also blocked 100% of malicious host-level probes. The contribution is integrating the layers so that the zero-trust principle holds throughout and after a compromise.
Evaluating Z3's Performance on Real Number Constraints
Empirical Strategies for Tactic Selection and Parallelization
Is solver guidance redundant for strong SMT implementations?
An exploration of domain-specific vs general improvements applied to Z3's string theories
implementation or using domain-specific guidance. We present a way to simulate domain-specific help automatically by reducing the search space based on the model solution, and we use it to compare two implementations of Z3′s string solver – Z3str3 (weaker) and Z3-Noodler (stronger) – with and without domain-specific help. We find that Z3-Noodler sees significantly less improvement than Z3str3 because 1) the additional “helping” constraints are in fact occasionally counterproductive and 2) Z3-Noodler solves equivalent problems much faster than Z3str3, so the relative overhead of the additional constraints is more noticed. ...
implementation or using domain-specific guidance. We present a way to simulate domain-specific help automatically by reducing the search space based on the model solution, and we use it to compare two implementations of Z3′s string solver – Z3str3 (weaker) and Z3-Noodler (stronger) – with and without domain-specific help. We find that Z3-Noodler sees significantly less improvement than Z3str3 because 1) the additional “helping” constraints are in fact occasionally counterproductive and 2) Z3-Noodler solves equivalent problems much faster than Z3str3, so the relative overhead of the additional constraints is more noticed.
Understanding SMT Solvers
Exploring Parallelization in Floating-Point Problems
Utilising SNP-SV Correlations to find SVs Associated with Alzheimer’s Disease
A Novel Approach to Identifying and Analysing Alzheimer’s-Related Structural Variants
catalytic activity. The results suggest that the SVs make an important contribution to the regulation of CAD-related gene expression and the overall risk of CAD. ...
catalytic activity. The results suggest that the SVs make an important contribution to the regulation of CAD-related gene expression and the overall risk of CAD.
Meet Your Onboarding Buddy
A Smart, Adaptive, and Conversational LLM Assistant to Smooth Your Software Onboarding Journey
In this thesis, we introduce a novel solution: the Onboarding Buddy system which uses large language models (LLMs) and retrieval augmented generation (RAG), enhanced by an automated approach for chain-of-thought (CoT) that improves onboarding for new and existing developers. It integrates natural language explanations available in the development environment with relevant information, code explanations, and project-specific guidance. The system architecture is agent-centric, including contextualization, onboarding agents, instruction step processors and message enhancement agents that cooperate in delivering comprehensive, customized support with minimal reliance on human mentors.
While effective in supporting the completion of tasks and reducing stress related to onboarding, feedback also revealed some areas for improvement, like better context awareness, explicit instructions, improved technical stability, and UX adjustments. In general, Onboarding Buddy is an excellent promise to smoothen the onboarding process and therefore increase developer productivity and job satisfaction.
The experimental results demonstrated the system's effectiveness: participants spent an average of 175 minutes actively engaged in the IDE, completed tasks with nearly 100\% accuracy, and gave high helpfulness ratings (3 out of 4). Task completion times averaged 50 minutes, with simpler tasks taking around 28 minutes and complex ones requiring 67 minutes. User feedback showed high satisfaction (3.35/4 for understanding, 3.15/4 for accuracy) and strong interest in such solutions (7.75/10). Interestingly, more experienced developers spent more time on tasks, suggesting a deeper exploration of the codebase. A strong positive correlation (0.70) between system usage frequency and perceived helpfulness indicated that increased engagement led to better outcomes.
In other words, while there are areas for improvement, such as context awareness and processing complex tasks, this research proves that LLM-based onboarding solutions are feasible and can have significant positive impacts on the software engineering onboarding process, thus laying the foundation for future progress in automated developer support and knowledge sharing for software development. ...
In this thesis, we introduce a novel solution: the Onboarding Buddy system which uses large language models (LLMs) and retrieval augmented generation (RAG), enhanced by an automated approach for chain-of-thought (CoT) that improves onboarding for new and existing developers. It integrates natural language explanations available in the development environment with relevant information, code explanations, and project-specific guidance. The system architecture is agent-centric, including contextualization, onboarding agents, instruction step processors and message enhancement agents that cooperate in delivering comprehensive, customized support with minimal reliance on human mentors.
While effective in supporting the completion of tasks and reducing stress related to onboarding, feedback also revealed some areas for improvement, like better context awareness, explicit instructions, improved technical stability, and UX adjustments. In general, Onboarding Buddy is an excellent promise to smoothen the onboarding process and therefore increase developer productivity and job satisfaction.
The experimental results demonstrated the system's effectiveness: participants spent an average of 175 minutes actively engaged in the IDE, completed tasks with nearly 100\% accuracy, and gave high helpfulness ratings (3 out of 4). Task completion times averaged 50 minutes, with simpler tasks taking around 28 minutes and complex ones requiring 67 minutes. User feedback showed high satisfaction (3.35/4 for understanding, 3.15/4 for accuracy) and strong interest in such solutions (7.75/10). Interestingly, more experienced developers spent more time on tasks, suggesting a deeper exploration of the codebase. A strong positive correlation (0.70) between system usage frequency and perceived helpfulness indicated that increased engagement led to better outcomes.
In other words, while there are areas for improvement, such as context awareness and processing complex tasks, this research proves that LLM-based onboarding solutions are feasible and can have significant positive impacts on the software engineering onboarding process, thus laying the foundation for future progress in automated developer support and knowledge sharing for software development.
Laying the foundation for building a Quantum Networking Benchmark suite using Quantum Network Applications
Evaluating the inclusion of the Clauser-Horne-Shimony-Holt game quantum network application
A test suite for quantum networks
Assessing an application’s effectiveness as a benchmark for quantum networks
The aim of this research is to determine the effectiveness of blind quantum computation - a quantum network algorithm - as a benchmark. We determine what changes to the system affect the results of executing this application, and we use this to determine whether it would be effective to use this application as part of a larger benchmarking suite. We do this by simulating a quantum network, and manually varying system parameters one by one, to see if they have an effect on the results.
What we observed from these experiments is that blind quantum computation is sensitive to almost all system parameters. This means that introducing an imperfection into almost any system parameter will negatively affect the results of the application. This means the application is useful as a full-system benchmark, because it is affected by almost the entire system. However, it also means that the application is less useful as a benchmark for individual parameters.
This means that to make the most useful benchmarking suite, blind quantum computation would have to be combined with other quantum network applications that are more suitable for benchmarking individual system parameters. ...
The aim of this research is to determine the effectiveness of blind quantum computation - a quantum network algorithm - as a benchmark. We determine what changes to the system affect the results of executing this application, and we use this to determine whether it would be effective to use this application as part of a larger benchmarking suite. We do this by simulating a quantum network, and manually varying system parameters one by one, to see if they have an effect on the results.
What we observed from these experiments is that blind quantum computation is sensitive to almost all system parameters. This means that introducing an imperfection into almost any system parameter will negatively affect the results of the application. This means the application is useful as a full-system benchmark, because it is affected by almost the entire system. However, it also means that the application is less useful as a benchmark for individual parameters.
This means that to make the most useful benchmarking suite, blind quantum computation would have to be combined with other quantum network applications that are more suitable for benchmarking individual system parameters.
A test suite for quantum network applications
Quantifying an application's ability to benchmark a quantum network
This paper examines the viability of using a specific quantum network application as a benchmark for quantum network systems. In order to quantify the application's ability to benchmark, we assess its sensitivity to changes in the properties of the system. These properties include link parameters, quantum gate properties, qubit coherence times, and measurement properties.
We use the BB84 protocol as the benchmarking application for this project, which is a Quantum Key Distribution scheme used to establish secure keys between two parties. In particular, we use the qubit error rate and the key generation rate as the performance metrics for the application. For the setup of the experiments, we prepare two system configurations: generic quantum device nodes with a depolarising error channel, and NV device nodes with a heralded link. In order to assess how the application behaves with changes to different system properties, we observe how the performance metrics change while individually varying system parameters and keeping all other parameters constant.
We find that the application is sensitive to changes in multiple parameters across both network configurations, such as link parameters, single qubit gate properties, and measurement properties. Contrarily, the application is not affected by changes to parameters such as two qubit gate properties and coherence times. We conclude that the BB84 protocol can be used as an individual localised test for the parameters it is sensitive to, and also in combination with other applications, in a more comprehensive benchmarking suite, that provide coverage for a broader range of parameters. ...
This paper examines the viability of using a specific quantum network application as a benchmark for quantum network systems. In order to quantify the application's ability to benchmark, we assess its sensitivity to changes in the properties of the system. These properties include link parameters, quantum gate properties, qubit coherence times, and measurement properties.
We use the BB84 protocol as the benchmarking application for this project, which is a Quantum Key Distribution scheme used to establish secure keys between two parties. In particular, we use the qubit error rate and the key generation rate as the performance metrics for the application. For the setup of the experiments, we prepare two system configurations: generic quantum device nodes with a depolarising error channel, and NV device nodes with a heralded link. In order to assess how the application behaves with changes to different system properties, we observe how the performance metrics change while individually varying system parameters and keeping all other parameters constant.
We find that the application is sensitive to changes in multiple parameters across both network configurations, such as link parameters, single qubit gate properties, and measurement properties. Contrarily, the application is not affected by changes to parameters such as two qubit gate properties and coherence times. We conclude that the BB84 protocol can be used as an individual localised test for the parameters it is sensitive to, and also in combination with other applications, in a more comprehensive benchmarking suite, that provide coverage for a broader range of parameters.
...