Nope, cls universal adds (0<<6) to resulting byte, so does effectively nothing. Passing `cls context` into encodeTag should however solve the issue without adding more params to function.