If I understand correctly, you will have 2 private keys (5J... and 5H... for example) combined to make a 3rd private key (5K...).
Could you send 0.10 BTC to the first address (5J...) and 0.10 to the 2nd (5H...) but send 100 btc to the 3rd (5K...)
Set up to be notified when one of the first 2 addresses are drained, this lets you know you have been compromised on 1 system.
Not exactly. The second key is not valid alone (it would be rejected) and the address created with it does not work on either key alone. But the address does work when you combine (using suitable EC math) the first key and the second key to make a final "real key". But you would only do that at the time you want to spend your balance.
I guess you could put a balance on the first key if you chose and it would be theoretically less secure since it's on your possibly compromised system. My intention wasn't to monitor the systems using honeypot keys. You could do that entirely independently with other keys if you wanted. But of course it may tell you nothing as a hacker may just wait until he sees a significant balance on the address.
---
If you wanted to test this out for yourself you would do the following, using the vanitygen programs (because at this time they are the only ones I know that do the partial key math, although there is a patched bitaddress.org around now that does key combining).
Sys #1 Run,
keyconv -G
Save the private key on usb #1. Save the public key on usb #2
Sys #2 Insert usb #2 and run,
vanitygen 1 -P <paste public key>
The private key and address would be saved on usb#2 now.
But if you want to test it then run,
keyconv -c <paste key#1> <paste key#2>
And it will output your "real key" and address should be same as above.
In real life I think I would lean towards using paper since moving usb keys between systems has the potential to carry an infection also.