maybe you dont need to put your btc address in the cube? perhaps x:x,x:x would work

I think bfgminer does not pass this info to the pool (i could be wrong about this)

so if you have 3 cubes connected to one single proxy they will appear as one worker to the pool

I actually run 3 instances of bfgminer proxy on my pi, each using about 10% cpu. still way less than slush's so I can use three command lines

for eligius you use an underscore character after your bitcoin address for a worker name ex: '_worker1'

so if you want to have separate stats and reporting on each cube use mutliple command proxy's on the same machine, just use a different port for each one and a different worker name in the command line

say for example you have a cube at 192.168.1.125 to keep it simple you can call him worker125 or cube125 or simply 125

command line

./bfgminer -o stratum+tcp://stratum.mining.eligius.st:3334 -O _125 --http-port 8125
./bfgminer -o stratum+tcp://stratum.mining.eligius.st:3334 -O _126 --http-port 8126
./bfgminer -o stratum+tcp://stratum.mining.eligius.st:3334 -O _127 --http-port 8127


the interesting thing with bfgminer is that you can use it to mine with other devices and act as proxy all with one instance
so you could be using it to run a butterfly labs miner, and a few usb sticks, and also have a cube connected to it's proxy. All three devices will appear in bfg miner and stats can be read there
but i think it all appears as one worker to the pool,

please if I am wrong about this some one let me know?